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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note (fix version 1.19.19):
Fixed issue where Sprites belonging to a Sprite Atlas aren't assignable to an AssetReferenceSprite field.