Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.4.5
1.5.0-pre.5
Issue ID
LOC-1024
Regression
No
NullReferenceException errors are thrown when opening a Scene that contains a modified prefab which changes are being tracked
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Observe the Console Window
Expected result: No error is thrown
Actual result: “Trying to update the managed reference registry with invalid propertyPath(likely caused by a missing reference instance" and multiple “NullReferenceException: Object reference not set to an instance of an object” errors are thrown
Reproducible with: 1.3.2 (2021.3.32f1, 2022.3.4f1, 2023.1.0a20), 1.4.4, 1.4.5 (2021.3.32f1, 2022.3.12f1, 2023.1.19f1, 2023.2.0b16, 2023.3.0a12)
Reproducible on: Intel macOS 14
Not reproducible on: No other environment tested
Note: Disabling and reenabling the “Game Ojbect Localizer (Script)” Component functions as a workaround
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
While attempting to reproduce the bug, we successfully triggered an error. However, the challenge lies in understanding the precise steps leading to this error state. Even with a new TMP GameObject, replicating the issue proves elusive. The error message suggests the disappearance of the managed reference, yet lacking a clear reproduction path hampers our ability to investigate effectively. Although we've implemented additional null checks to mitigate potential references, resolving the fundamental issue remains elusive. Any insights or guidance on replicating the error would be greatly beneficial in advancing our troubleshooting efforts.