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
- [VFX] Missing Expand Option with Output Slot
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
Resolution Note (fix version 1.19.19):
Fixed issue where Sprites belonging to a Sprite Atlas aren't assignable to an AssetReferenceSprite field.