04-10-2012 08:28 AM - edited 04-10-2012 08:30 AM
My app needs to save project state upon closing, so I'm handling the NAVIGATOR_EXIT message and starting my save to shared storage then.
The problem is, the project files can be quite large (up to 10Mb) depending on the user content and because the app only has ~500ms to exit before the system forcefully shuts it down, I'm running into cases where the auto-save is failing to complete. I can handle the case of the file not being completely saved when starting up next time, but it means a bad user experience because they will potentially have lost work.
The API reference says an app can call navigator_extend_timeout() to allow it up to 30s to create its window. I'd like to know if there's an equivalent to extend the forced app closed timout in the same way or something equivalent?
I don't need 30 seconds, just 1-2 more...even if it's running in the background at low priority with no window at that point.
Solved! Go to Solution.
04-10-2012 08:45 AM
04-12-2012 01:57 PM
This is a planned feature as part of BPS.
It will be coming soon in a future release.
Please stay tuned!
04-12-2012 10:15 PM
Thanks, even if the app isn't being rendered anymore, a bit of extra time to save/clean-up would be great.