RESOLVED DUPLICATE of bug 247147 247087
iOS 16.1 regression of SharedWorker when a process doesn't have com.apple.developer.web-browser entitlement
https://bugs.webkit.org/show_bug.cgi?id=247087
Summary iOS 16.1 regression of SharedWorker when a process doesn't have com.apple.dev...
dmt021
Reported 2022-10-26 14:23:36 PDT
Starting from iOS 16.1 WKWebView can't load pages with SharedWorker, if an app doesn't have "com.apple.developer.web-browser" entitlement. Samples: https://mdn.github.io/dom-examples/web-workers/simple-shared-worker/ https://vc.ru The NetProcess terminates the WebProcess, and renders the whole WKWebView crashed. In case the "com.apple.developer.web-browser" entitlement is present it works fine. The issue can be reproduced on iOS 16.1 with a basic WKWebView, or in apps: Google - https://apps.apple.com/ru/app/google/id284815942 Yandex - https://apps.apple.com/ru/app/яндекс-с-алисой/id1050704155 The issue can NOT be reproduced in: Chrome - https://apps.apple.com/ru/app/chrome-браузер-от-google/id535886823 Yandex Browser - https://apps.apple.com/ru/app/яндекс-браузер/id483693909 or on any iOS version prior 16.1
Attachments
Radar WebKit Bug Importer
Comment 1 2022-10-26 15:12:38 PDT
youenn fablet
Comment 2 2022-10-27 02:47:08 PDT
Can you share the crash log?
dmt021
Comment 3 2022-10-27 03:54:03 PDT
Clarification: The app doesn't crash. Only the WebProcess crashes. There is this message in the log. [Process] 0x136010a18 - [pageProxyID=6, webPageID=7, PID=57025] WebPageProxy::processDidTerminate: (pid 57025), reason=RequestedByNetworkProcess And: com.apple.WebKit.Networking Received an invalid message 'WebSharedWorkerObjectConnection_FetchScriptInClientReply' from WebContent process 5, requesting for it to be terminated.
Leo Balter
Comment 4 2022-10-28 14:08:56 PDT
Chris Dumez
Comment 5 2022-10-28 14:16:42 PDT
Also see this for some details (and a workaround): https://developer.apple.com/forums/thread/718757?page=1#734292022 *** This bug has been marked as a duplicate of bug 247147 ***
Note You need to log in before you can comment on or make changes to this bug.