Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.8.3
Issue ID
ADDR-1234
Regression
No
Different AssetReferenceSprite cannot be selected in the Inspector when its Addressable name is the same
How to reproduce:
1. Open the attached project "case_1247743-AddressableAsset"
2. Open the Scene "SampleScene"
3. Select the GameObject "Test" in the Hierarchy
4. Open the dropdown of Addressable Assets of the field "Sprite Reference" in the Test (Script) component in the Inspector
5. Select the second Addressable Asset "sprite" in the dropdown
Expected results: the second Addressable Asset "sprite" as a "Sprite Reference" is selected
Actual results: the first Addressable Asset "sprite" as a "Sprite Reference" is selected even though the other one was selected
Reproducible with: 0.7.4-preview, 1.8.3 (2018.4.23f1, 2019.3.14f1, 2020.1.0b9, 2020.2.0a12)
Could not test with: 0.6.8-preview because AsyncOperationHandle was not introduced
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Add comment