Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2019.1.X
Votes
1
Found in
2019.1.0a10
Issue ID
1104514
Regression
No
WASM streaming doesn't work using Build&Run Release builds
-e: when trying to have your build served from the built-in webserver it fails when WASM streaming is enabled
-repro:
--open attached project/create new one
--enable WASM streaming in player settings
--make sure Development Build is unchecked
--Build&Run WebGL
--NOTICE that the build fails to run in the brower and errors are logged into the console
---wasm streaming compile failed: TypeError: Response has unsupported MIME type
---falling back to ArrayBuffer instantiation
---failed to asynchronously prepare wasm: CompileError: wasm validation error: at offset 4: failed to match magic number
---CompileError: "wasm validation error: at offset 4: failed to match magic number"
Comments (5)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animator Controller Layer name stays unchanged in Layers tab when renamed from Inspector
- [RenderingDebugger]Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
- [Mac] Glitchy visual artifacts appear when moving around a scene with Sphere Handles
- Crash on memcpy_repmovs when selecting NavMesh Agent objects while in Play Mode in a specific scene
Ntalam
Oct 07, 2021 09:35
not fixed in 2021.1.21f1
Stream
Mar 29, 2021 06:37
Still not fixed in 2020.3 LTS