You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On native iOS and Android, there appears to be an issue with loading a WASM file via fetch (which uses CapacitorHttp at a lower level) and calling WebAssembly.instantiateStreaming() on it. The repro uses the esri ArcGIS API for JavaScript v3.x which loads a WASM file. I don't know much about using WASM, so I did not tear down to a more minimal repro.
Native iOS withoutCapacitorHttp, native Android withoutCapacitorHttp, and Web work fine.
Expected Behavior
Native iOS and Android should work like the Web's fetch when loading a WASM file in this way.
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Capacitor, please create a new issue and ensure the template is fully filled out.
Bug Report
Capacitor Version
Platform(s)
Native iOS
Native Android
Current Behavior
On native iOS and Android, there appears to be an issue with loading a WASM file via
fetch
(which usesCapacitorHttp
at a lower level) and callingWebAssembly.instantiateStreaming()
on it. The repro uses the esri ArcGIS API for JavaScript v3.x which loads a WASM file. I don't know much about using WASM, so I did not tear down to a more minimal repro.Native iOS without
CapacitorHttp
, native Android withoutCapacitorHttp
, and Web work fine.Expected Behavior
Native iOS and Android should work like the Web's
fetch
when loading a WASM file in this way.Code Reproduction
https://github.com/KevinKelchen/capacitor-http-wasm-issue#steps-to-reproduce
Other Technical Details
npm --version
output: 8.15.0node --version
output: v16.17.0pod --version
output (iOS issues only): 1.11.3Additional Context
The text was updated successfully, but these errors were encountered: