I would vote for defaulting to WebViewAssetLoader but still allow using
file:// from a config.xml preference for the people that are not ready to
move on.
But on cordova-ios 6 I think we ended up defaulting to file:// and use the
schemes only as opt-in.
About migrating data, I don't think that's o
I also agree.
I think we should move forward with these changes and use the
WebViewAssetLoader by default.
If must, we could write a blog post explaining how to use Norman's plugin for
data migration. But I do not know if the plugin is complete to cover all data
sources and fits this case.
I
To counter a bit, all of my apps are using the standard Cordova
Android WebView, and store all their data in the browser's indexedDB.
I've had no issues with file URLs (although I expect that will change
with API 30 enforcement).
Losing data in an app update is unacceptable, and for many apps it
w
My understanding is that file urls can technically continue working,
but the defaults changed and some settings need to be enabled, and
some of them are now deprecated and will stop working at some point in
the future.
I think defaulting to the old behavior is ok when doing minor releases
(not jus
