Data persistence in iOS Cordova App after App termination

[kjsdesigns]

Kudos to the Forerunner dev team. Great product.

I have a similar but more specialized use-case to the following older issue:
#120

My use case is as follows:

1. User installs Cordova based App (iOS only)
2. User opens the App, logs in
3. User goes offline
4. User performs actions while offline, we store the results in forerunner
5. User logs out
6. User goes back online
7. User logs in
8. Data from forerunner successfully sent to server
9. User goes offline
10. User performs actions while offline, we store the results in forerunner
11. User terminates the app (exits / reboots device)
12. User opens up the app again
13. User logs back in
14. Forerunner data stored in step 10 is gone

Can anyone suggest a solution that that allows data persistence even after the app is terminated?

[Irrelon]

Hi ya, this is an interesting issue. I am aware that iOS can clear the indexedDB data if it considers the device is running low on space.

I am assuming from your description that you are using the persistence plugin and doing save() and load() when required.

A user on here found that he could use a cordova plugin to LocalForage that stored data in app storage instead of indexeddb and that solved the issue. I cannot remember the localforage plugin name but a google for it should bring it up.

Can you let me know if that helps at all?

Cheers,

Rob

[kjsdesigns]

Thank you - will follow-up on the localForage side and let you know.

[Irrelon]

Hey, how did it go? Did you manage to get the storage to stay put?

[kjsdesigns]

Sorry for the delay. No, not yet - though the author of localForge suggested he thought his library should fix the issue. For now the issue with my application is not being prioritized. I will follow-up if we do try localForge in the future.