Created attachment 432585 [details] Trying to invoke unregister from dev console Overview ServiceWorkerRegistration.unregister method fails in WKWebView. Error message "TypeError: Job rejected for non app-bound domain" is displayed in console. The current domain is listed as a App Bound Domain and service worker registration is also successful. But the issue is with unregister method. I have also attached a video of the error. In the video I have tried to invoke unregister method from Dev Console. Steps to Reproduce 1. For an App Bound Domain. Register a service worker 2. After the service worker is activated try to unregister it 3. Sample Code navigator.serviceWorker.getRegistration() .then(registration => registration.unregister()) .then(() => console.log('Unregistration success')) .catch(error => console.error('Unregistration failed', error)); Actual Result unregister method fails with the error - "TypeError: Job rejected for non app-bound domain". Expected Result Service worker registration gets unregistered Environment Device: iPad Mini 4 OS: iOS 14.7 (18G5042c)
App bound domains -> Kate :)
<rdar://problem/80264108>
Created attachment 434180 [details] Patch
Committed r280319 (239967@main): <https://commits.webkit.org/239967@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 434180 [details].
Hi Thanks the fix. Could you please provide the following info as well - In which iOS version will this changes be released ? - Is it possible to upgrade the webview locally for trying out the new fix ?
(In reply to Kiran Satheesan from comment #5) > Hi > > Thanks the fix. > > Could you please provide the following info as well > > - In which iOS version will this changes be released ? > - Is it possible to upgrade the webview locally for trying out the new fix > ? Bugzilla tracks the WebKit Open Source Project which is not in charge of future iOS releases, so I have no comment there.
This should be in the latest iOS 15 beta, so you can test it there.
*** Bug 227918 has been marked as a duplicate of this bug. ***