Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2019.4.21f1
2020.2
2021.1
2021.2
Issue ID
1318125
Regression
No
[WebGL][Bolt] "Failed to deserialize scriptable object" error is thrown when launching WebGL Player built with Bolt
How to reproduce:
1. Open the attached project
2. Make a WebGL Build
3. Open the built WebGL Player on a browser
4. Open the Developer Console (shortcut F12)
5. Inspect the Console
Expected result: Scriptable Objects are deserialized successfully
Actual result: "Failed to deserialize scriptable object" error is thrown
Reproducible with: 2019.4.21f1, 2020.2.7f1, 2021.1.0b9, 2021.2.0a7
Couldn't test with: 2018.4.32f1 (Provided project breaks)
Note: Not reproducible in the Standalone Player
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
- Console Warning -- KeyboardIconAtlas sprite Input Outline goes beyond the boundary of the Sprite rect.
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
Resolution Note:
The issue is fixed if an "AOT Pre-Build" (Tools -> Bolt -> AOT Pre-Build) is started before the project is built. This is not a bug. Unity 2021 and onwards don't support Bolt and use VisualScripting instead. VisualScripting automatically runs the "AOT Pre-Build" when a project is built.