Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.3.7
Issue ID
ADDR-3823
Regression
No
AssetReference displays that the value is not set when the reference is set
Reproduction steps:
1. Open the attached “IN-89996” project
2. Open the Addressables Groups window (Window > Asset Management > Addressables > Groups)
3. Add “Scenes/Sample.png” Asset to the “Default Local Group” Group
4. Open the “Scenes/SampleScene” Scene
5. Select the “Sample” GameObject in the Hierarchy window
6. Assign the “Scenes/Sample.png” Asset to the “Asset Reference” field in the Inspector window
7. Delete the “Scenes/Sample.png” Asset in the Project window
8. Check the “Asset Reference” field under the “Sample Script” component
Expected result: The field displays that the Asset is missing
Actual result: The field displays “None”
Reproducible with: 1.20.0 (2021.3.45f1), 1.22.3 (2022.3.53f1), 2.2.2, 2.3.1 (6000.0.30f1, 6000.1.0a7)
Reproducible on: Windows 10
Not reproducible on: No other environments tested
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
- Intercepted Events text is hardly visible in Inspector window for UI elements when Editor theme is set to Light
- [Hierarchy V2] Add new Query Block window contains a typo in the Hierarchy Search Area block
- Scene is not rendered in Player when ran with -force-d3d12 argument and GPU Resident Drawer enabled
- “Failed to load” window appears when a package’s docked window is opened and the package is uninstalled
- Properties window is not closed when the GameObject is deleted and the Properties window is not focused
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.