On 13 Jun 2018, at 9:44pm, skywind mailing lists <mailingli...@skywind.eu> wrote:
> The operation system is iOS (therefore, it is difficult to remove the battery > and do several tests after each other) (First paragraph is background for others reading this message.) An iOS application which is running is supposed to receive a 'quit now' notification if the phone wants it to close. This notification allows it to save context and close files. The documentation for iOS explains this and tells developers that their Apps must deal with this notification correctly. The documentation doesn't mention that there's a situation where the 'Quit now' notification is not sent. This is where the phone thinks it's going to run out of power before all the running Apps, including all the background ones, have had a chance to do their filehandling. And you can simulate this situation. So here's how to simulate an 'out of power' shutdown situation where your app doesn't get the 'quit now' notification: Have the application running. Switch it to background by switching some other application to foreground. Make sure that the phone is running off of its own battery power. It doesn't matter what your charge level is. Double-click the home button to bring up the task manager interface. Find the display for your application and, without bringing it to the foreground, drag it upwards to terminate the App. In this situation the App will be terminated without the 'quit now' notification. It simulates the 'running out of batter power now' situation where the phone notifies only the foreground application to quit. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
