Search Issue Tracker
Fixed in 1.6.1
Votes
0
Found in [Package]
1.2.2, 1.3.8
Issue ID
1199800
Regression
No
[Addressables] AssetReference.RuntimeKeyIsValid returns false for sub-objects even when GUID matches
How to reproduce:
1. Open the attached project ("case_1186801-AddressableError.zip")
2. Open the repro scene ("SampleScene")
3. Build Player Content
4. Make sure that "AssetReferenceCarrier" object in the Hierarchy has both AssetReference fields set
4. Enter Play Mode
5. Inspect the console
Expected results: RuntimeKeyIsValid returns true because key GUIDs are the same
Actual results: RuntimeKeyIsValid returns false
Reproducible with: 2018.4.13f1, 2019.2.13f1, 2019.3.0b12, 2020.1.0a14
Couldn't test with 2017.4 (no Package Manager)
Reproducible with package versions: 1.2.2, 1.3.8 (couldn't test with older versions because they lacked public GUID variable)
Notes:
1. Loading the sprite with the "invalid" key still succeeds and returns the correct sprite
2. It seems that the GUID parsing fails to parse subobjects name out of the GUID
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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
Resolution Note (fix version 1.6.1):
This will be resolved in the next build of addressables.