Search Issue Tracker
Fixed
Won't Fix in 1.0.X
Fixed in 1.1.0 - Entities
Votes
1
Found in [Package]
1.0.0
Issue ID
ECSB-300
Regression
No
“NullReferenceException" errors are thrown in Play mode when subscene editing is disabled
Reproduction steps:
1. Open the attached “InconsistentPrefabBehaviorRepro.zip“ project
2. Open the “Repro” scene
3. Enable Editing for “ecs” subscene in Hierarchy window and enter Play mode
4. Exit Play mode and observe the Console
5. Disable editing for “ecs” subscene and enter Play mode
6. Exit Play mode and observe the Console
Expected result: No errors are thrown
Actual result: “NullReferenceException: Object reference not set to an instance of an object
Unity.Entities.BlobAssetReferenceData.get_IsProtected () (at ./Library/PackageCache/com.unity.entities@1.0.0-pre.65/Unity.Entities/Blobs.cs:373)” errors are thrown
Reproducible with: 1.0.0-pre.65 (2022.2.16f1, 2023.1.0b13, 2023.2.0a11)
Could not test with: 0.17.0-preview.42 (2020.3.47f1), 0.51.1-preview.21 (2020.3.47f1, 2021.3.23f1) (Errors in the Console)
Reproduced on: macOS Monterey 12.6 (Intel), Windows 10 (by the reporter)
Note: Couldn't test in Build (Errors in the Console)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 1.1.0 - Entities):
Now blob asset references should work in unmanaged shared components.
Resolution Note (1.0.X):
This is not fixed in 1.0. It's fixed in 1.1.