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
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
Resolution Note (2019.2.X):
We are currently working on a new WebGL loader and we will address this there.