Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.8f1
2018.3.0a1
2019.1.0a1
Issue ID
1091040
Regression
No
[WASM] UnityLoader doesn't throw an error when wasmCodeUrl path is invalid
How to reproduce:
1. In the attached "TestFor1091040.zip" project go to TestBuild -> Build
2. In the TestBuild.json file modify the "wasmCodeUrl" path to make it incorrect
3. Run the build in a browser
4. Open browser's console
5. Notice that the build doesn't load and there's no error indicating that the wasmCodeUrl path is invalid
Expected result: UnityLoader throws an error for an invalid path
Actual result: UnityLoader doesn't throw an error for an invalid path
Reproducible with: 2018.3.1f1, 2019.1.0a13
Note: UnityLoader.js has this code added to it for the error handling:
UnityLoader.Error.handler = function(e, t) {
console.log("Captured error: "+e);
}
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2019.2.X):
We are currently working on a new WebGL loader and we will address this there.