Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.21.15
Issue ID
ADDR-3496
Regression
No
NullReferenceException and TreeView errors are thrown when assigning an Addressable Asset in the Inspector when a null sub-assets exist in the project
How to reproduce:
1. Open the “AssetReferenceT_repro.zip“ project
2. In the Project window click on the “MyScriptableObject_1“ asset
3. In the Inspector window, attempt to assign an asset to the “Scriptable Obj“ field
4. Observe the “Select Addressable Asset“ window and the Console
Expected result: "MyScriptableObject_1" and "MyScriptableObject_2" appear in the “Select Addressable Asset“ window and no errors are seen in the Console
Actual result: Errors are thrown and the “Select Addressable Asset“ window is empty
Reproducible with: 1.21.15 (2021.3.29f1, 2022.3.8f1, 2023.1.10f1, 2023.2.0b6, 2023.3.0a2)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Workaround: Dragging the asset from the Project window
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.