Martin Kleinschrodt commented on CB-11974:

> My suggestion is in the interim, before migrating users to wkwebview, write 
> the localStorage key data to a file as well as localStorage (duplicate the 
> data in two locations).

> Then for the next update, read from this file to write to localStorage. This 
> avoids the situation where you really need to know file locations of the 
> webkit storage, but rely on a reliable, consistent, interim format.

This does not work for obvious reasons. The suggested interim version *has to 
be installed by all existing users before updating to the "final" version*. If 
a user skips the interim version, which is almost guaranteed to happen unless 
it is around for a very long time, the migration will fail and the user will 
lose all their data. If you don't want to integrate this into cordova-ios, 
fine, but please don't suggest "solutions" that simply are not workable.


> wkwebview LocalStorage Persistence For Existing Users
> -----------------------------------------------------
>                 Key: CB-11974
>                 URL: https://issues.apache.org/jira/browse/CB-11974
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-plugin-wkwebview-engine
>            Reporter: Charles Vanderhoff
>            Priority: Major
>              Labels: wkwebview-known-issues
> There are a number of apps out there that rely on localstorage to store 
> session / user data. We really need a way to transfer this data to the 
> wkwebview-engine so existing users are not left out in the cold.
> Crosswalk handles this process automatically by migrating that data to the 
> new browser when the plugin is installed and first run on an existing user's 
> device. It would be really, really awesome if this plugin handled this issue 
> the same way.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to