Search Issue Tracker
Fixed
Votes
1
Found in [Package]
1.9.2
Issue ID
ADDR-1300
Regression
Yes
[Addressables] Sprites that are part of a Sprite Atlas cannot be loaded and result in InvalidKey exceptions
How to reproduce:
1. Open user-submitted project (Bug Report.zip)
2. Open the Addressable Groups window and build the addressables
3. Open the MainScene and check that the 'Sprite Renderer' GameObject has the option 'Use Generic Sprite' unchecked
4. Enter Play Mode
Expected result: the sprite is loaded
Actual result: the sprite is not loaded, 2 exceptions are thrown
Reproducible with: 2018.4.24f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a15 - Addressables 1.9.2, 1.10.0
Not reproducible with: 2018.4.24f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a15 - Addressables 1.8.4
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 Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
Resolution Note:
sprites are generally built as both Texture2D and Sprite objects. If they are in a SpriteAtlas, they are only built as type Sprite because the texture is in the atlas. We were putting them in the catalog as only Texture2D, when it should have been only Sprite. It was a problem with the typing in the catalog.