Stuck on an issue?

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.

iOS 15 Breaks with custom headers

See original GitHub issue

Bug Report

We are busy reviewing our apps to get ready for iOS 15 changes. We have noticed when using a basic JS fetch and supplying custom headers the encounters an error. This is problematic especially if the the fetches require headers such as tokens, authorization ect.

This appears to only occur when using the scheme and host name options.

<preference name="scheme" value="http" />
<preference name="hostname" value="localhost" />

Problem

Web Error Failed to load resource: WebKit encountered an internal error

XCode Error

[Process] 0x128ad1000 - NetworkProcessProxy::didClose (Network Process 0 crash)
[assertion] Error acquiring assertion: <Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}>

What is expected to happen?

At least a success or catch error should return on the js fetch

What does actually happen?

Xcode returns a error and the fetch does not execute

Information

We have tested a simple fetches, one without custom headers and one with custom headers. We also setup a minimal app without any plugins to isolate the issue. This issue does seem to originate from CDVWebViewEngine when scheme and hostname are used.

This all still works on iOS 14.6, so it appears to be something on iOS 15.0 that has changed.

Command or Code

What works

fetch(`https://everydaydigital.co.za/lab/tests/test.php`).then(r => {
	return r.json();
}).then(response => {
	console.log(response);
}).catch(err => {
	console.warn(err);
});

What doesn’t work

fetch(`https://everydaydigital.co.za/lab/tests/test.php`,{
    headers : {
        'token' : '123456789'
    }
}).then(r => {
     return r.json();
}).then(response => {
    console.log(response);
}).catch(err => {
   console.warn(err);
});