Search Issue Tracker
Fixed in 1.8.3
Votes
14
Found in [Package]
1.4.0, 1.5.0
Issue ID
1202034
Regression
Yes
[Addressables] InvalidKeyException is thrown when using LoadAssetsAsync<Sprites> on a folder and using Asset Database play mode
How to reproduce:
1. Open the attached project ("case_1202034-Repro.zip")
2. Open the repro scene ("SampleScene")
3. Build Player Content using "Asset Database" mode
4. Enter Play Mode
Expected results: The sprite is loaded and can be seen on the white cube
Actual results: InvalidKeyException is thrown and no sprites are loaded
Reproducible with: 2018.4.15f1, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18
Couldn't test with 2017.4 (no package manager)
Reproducible with package: 1.4.0, 1.5.0
Not reproducible with package: 1.3.8
Notes:
1. The issue does not reproduce when "Simulate Groups" or "Existing Build" build modes are used
2. Couldn't reproduce the issue with GameObject type assets
3. Reproduces with both Asset Database V1 and V2
Comments (3)
-
JohnRocket
Jun 21, 2020 15:16
This is back in 1.10.0
-
aelrhermoul
Mar 21, 2020 20:59
This is also occurring in 1.6.2 and in 1.7.4.
-
iamarugin
Feb 21, 2020 12:17
Hello. Any news about this issue?
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.8.3):
refactored how subobjects and sprites are handled