Search Issue Tracker
Active
Under Consideration for 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.32f1
6000.1.0a9
6000.2.0a1
6000.3.0a1
6000.4.0a1
Issue ID
UUM-91610
Regression
No
Error "InvalidOperationException: An error occured while deserializing asset reference" is thrown when deserializing a BlackboardVariable that is a dynamically loaded monobehavior
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Samples/Behavior/1.0.6/Runtime Serialization/Serialization.unity” Scene
3. Enter the Play Mode
4. Click the Button with the text “Assign Variable”
5. Click “Save“
6. Click “Write“
7. Exit the Play Mode
8. Enter the Play Mode
9. Click “Load from File“
10. Observe the Console
Expected result: No Errors exist
Actual result: Errors “InvalidOperationException: An error occured while deserializing asset reference GUID=[7a89880255e2246de83870fb9c1e9803]. Asset is not yet loaded and will result in a null reference.“ and “NullReferenceException: Object reference not set to an instance of an object“ are present
Reproducible with: 6000.0.32f1, 6000.1.0a9
Could not test with: 2022.3.55f1 (Library\PackageCache\com.unity.behavior@1.0.6\GraphEditor.cs(9,6): error CS0246: The type or namespace name 'UxmlElementAttribute' could not be found)
Reproducible on:
Play Mode
Not reproducible on:
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- Discussions thread: https://discussions.unity.com/t/deserializing-globalobjectid-issue/1571711
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment