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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 1.6.1):
This will be resolved in the next build of addressables.