3 ms·

That doesn't make it any less of a problem and if apps under iOS 13 loose data while they didn't under iOS 12, then finger pointing and putting fingers into the

• tpmoney 7y ago
  It depends on whether the issue is that iOS is terminating background apps before they’re able to flush to disk or whether the issue is that the app isn’t flushing to disk when sent to the background. If the former that is Apple’s problem to fix. If the later they are absolutely right to point the blame where it belongs, on the developers who didn’t code to the platform standards. If it is the later, those same apps would have lost data under iOS 12, and they were just lucky that the termination algorithms were less aggressive.
  • diffeomorphism 7y ago
    > If the later they are absolutely right to point the blame Good for them, but as a user I don't care whose fault it is. The only thing I see is that my (very expensive) iThingy is not working right after the update.
• setr 7y ago
  It's the constant problem for libraries: developers relying on implementation details that were not guaranteed. Microsoft has traditionally bent over backwards to support such misbehaving applications (eg simcity getting application-specific code in windows 95 release [0]), whereas Apple has traditionally allowed things to break. It shouldn't be very surprising they continued that behavior today, unless it's the case that it was guaranteed in ios12 and broken in ios13. [0] https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost-the-api-war/ https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost...