[
https://issues.apache.org/jira/browse/CB-11974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah resolved CB-11974.
-----------------------------------
Resolution: Workaround
Thanks for the workaround. Resolving since it is not really a bug.
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.
With the next major platform version of cordova-ios, the wkwebview plugin will
be baked in, so "migration" will be easier. When the user who is still on
UIWebView has migrated their data to the interim format, you can switch to
WKWebView usage that will then ingest this data.
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
