Bug 243120

Summary: REGRESSION (iOS 16 beta 3) - WebAssembly not working in SFSafariViewController
Product: WebKit Reporter: kacilambeth <kacilambeth>
Component: WebAssemblyAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Critical CC: saam, webkit-bug-importer, ysuzuki
Priority: P2 Keywords: InRadar
Version: Other   
Hardware: iPhone / iPad   
OS: Other   
Attachments:
Description Flags
Console log from minimum repro none

Description kacilambeth@nianticlabs.com 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
Comment 1 Radar WebKit Bug Importer 2022-07-22 22:18:58 PDT 
<rdar://problem/97471640>
Comment 2 Yusuke Suzuki 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 ;)
Comment 3 kacilambeth@nianticlabs.com 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).
Comment 4 Yusuke Suzuki 2022-09-19 19:27:41 PDT 
It is fixed in the new betas :), thanks!