RESOLVED FIXED 243120
REGRESSION (iOS 16 beta 3) - WebAssembly not working in SFSafariViewController
https://bugs.webkit.org/show_bug.cgi?id=243120
Summary REGRESSION (iOS 16 beta 3) - WebAssembly not working in SFSafariViewController
kacilambeth@nianticlabs.com
Reported 2022-07-22 16:56:13 PDT
Created attachment 461150 [details] Console log from minimum repro SFSafariViewController WebAssembly regression between iOS 15.5 and 16 beta 3 Website running WebAssembly opened within SFSafariViewController causes error. Minimum repro test: https://5oqkgi.csb.app/ Expectation: The screen shows text with "1+2=3" Result: The screen is blank Console logs from repro (also attached): [Error] Unhandled Promise Rejection: ReferenceError: Can't find variable: WebAssembly (anonymous function) (5oqkgi.csb.app:17) asyncFunctionResume (anonymous function) promiseReactionJobWithoutPromise promiseReactionJob Testing for whether window.WebAssembly was present, shows undefined: > window.WebAssembly < undefined As a result of this bug, Niantic WebAR sites are broken impacting major brands including: Paramount Pictures, Universal Pictures, Marvel, LA Dodgers, MGM, Xbox, & More Example of impacted Paramount Pictures website (Opened in SFSafariViewController): https://whatsmycallsign.com Expected result: After user enters their name, and allows camera permissions, they see their front camera feed with an AR face effect. Actual result on iOS 16 beta 3 SFSafariViewController: User enters their name, and sees an incorrect iOS version message triggered by a caught WebAssembly error
Attachments
Console log from minimum repro (31.77 KB, image/png)
2022-07-22 16:56 PDT, kacilambeth@nianticlabs.com
no flags
Radar WebKit Bug Importer
Comment 1 2022-07-22 22:18:58 PDT
Yusuke Suzuki
Comment 2 2022-07-23 15:04:47 PDT
Thank you for your report! I confirmed this bug and it turned out the SafariViewController side issue. Safari engineer is looking into it ;)
kacilambeth@nianticlabs.com
Comment 3 2022-08-29 13:12:47 PDT
(In reply to Yusuke Suzuki from comment #2) > Thank you for your report! I confirmed this bug and it turned out the > SafariViewController side issue. Safari engineer is looking into it ;) Has this been resolved? I am not seeing this error in beta 7 (20a5356a).
Yusuke Suzuki
Comment 4 2022-09-19 19:27:41 PDT
It is fixed in the new betas :), thanks!
Note You need to log in before you can comment on or make changes to this bug.