Search Issue Tracker
Fixed
Fixed in 1.19.19
Votes
0
Found in [Package]
1.19.11
Issue ID
ADDR-2652
Regression
Yes
[Addressables] Sprites belonging to a Sprite Atlas aren't assignable to an AssetReferenceSprite field
How to reproduce:
1. Open the user's attached "ZD_1193866_SpriteRef" project
2. Open the "SampleScene" Scene
3. Select the "GameObject" GameObject in the Hierarchy
4. Drag the "New Sprite Atlas" Sprite Atlas from the Project Browser to the "Sprite Reference" field in the Inspector
Expected result: Sprites belonging to the "New Sprite Atlas" Sprite Atlas get assigned to the AssetReferenceSprite field
Actual result: Nothing gets assigned
Reproducible with: 1.19.11 (2019.4.37f1, 2020.3.32f1), 1.19.19 (2021.2.18f1, 2022.1.0b14, 2022.2.0a9)
Not reproducible with: 1.19.9 (2019.4.37f1, 2020.3.32f1)
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (fix version 1.19.19):
Fixed issue where Sprites belonging to a Sprite Atlas aren't assignable to an AssetReferenceSprite field.