Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
origin is null for requests sent with window.fetch on WKWebView engine
See original GitHub issueIssue Type
- Bug Report
- Feature Request
- Support Question
Description
I’m attempting to upgrade cordova-ios from 5.1.1 to 6.0.0 for a project. At the same time, I’m also trying to migrate from uiwebview to wkwebview since that’s the new default. And uiwebview is going to be deprecated anyways.
Following the release note, I’ve managed to get the standard xhr working by setting the scheme and hostname preferences in config.xml
However the requests sent with window.fetch still have the origin set to null despite the custom scheme configuration.
Is that the expected behavior, and I will have to migrate to some other plugin to replace the window.fetch functionality? Is there something else that I’m missing?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
in
CordovaLib/Classes/Private/Plugins/CDVWebViewEngine/CDVWebViewEngine.mafterWKWebViewConfiguration* configuration = [[WKWebViewConfiguration alloc] init];add[configuration setValue:@"TRUE" forKey:@"allowUniversalAccessFromFileURLs"];can fix api failSame problem when the axios is used.