eradin commented on issue #883:
URL: https://github.com/apache/cordova-ios/issues/883#issuecomment-643657781


   > 
   > 
   > You should migrate your app to use schemes, which should solve this issue, 
among other `file://` related issues with the WKWebView. Do note however that 
switching schemes will cause you lose web storage such as indexedDB or local 
storage, as the origin of your app will change.
   > 
   > If you must use the `file://` scheme, then I would advise sticking with 
`[email protected]` for the time being. You need to use a plugin such as 
https://github.com/oracle/cordova-plugin-wkwebview-file-xhr, but it currently 
expects the wkwebview engine to be installed, which is incompatible with 
cordova-ios@6. I've raised an issue at 
[oracle/cordova-plugin-wkwebview-file-xhr#55](https://github.com/oracle/cordova-plugin-wkwebview-file-xhr/issues/55)
 to see if they can update the plugin to support cordova-ios@6.
   
   I have confirmed that removing all WKWEBVIEW plugins and adding the 
config.xml directives:
   
   ```
   <preference name="scheme" value="app" />
   <preference name="hostname" value="localhost" />
   ```
   
   Works for [email protected].  This was not obvious from the blog release 
notes nor were these explained on what they do and how to use them 
(documentation needs updating).  They apparently implement an "app" scheme and 
override the file:// scheme which will be rejected by WKWEBVIEW.  I have 
confirmed that this also works with plugins, file and fileopener2.  My app 
doesn't use inappbrowser so I can't confirm that one.
   
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to