Search Issue Tracker
Fixed in 1.8.3
Votes
1
Found in [Package]
1.3.3, 1.6.0
Issue ID
1214409
Regression
Yes
[Addressables] ArgumentOutOfRangeException error is thrown when loading the same catalog twice using LoadContentCatalogAsync
How to reproduce:
1. Open the attached project ("case_1214409-AASCatalogtest.zip")
2. Open the repro scene ("SampleScene")
3. Build Player Content
4. Enter Play Mode
5. Inspect the Console
Expected results: No errors are thrown
Actual results: "ArgumentOutOfRangeException: Index was out of range." error is thrown
Reproducible with: 2018.4.16f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a22
Couldn't test with: 2017.4 (package not supported)
Reproducible with package versions: 1.3.3, 1.6.0
Not reproducible with package versions: 1.1.5, 1.2.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
- Progress indicator in Meta Quest Build Profile configuration is barely visible
- Slightly transparent objects disappear completely in Web Player when using RenderGraph
- Visual Scripting Components are hidden behind a throbber when Multiplayer Play Mode is running with at least one local instance
- Video Player does not throw an error when playing a video with unsupported encoding settings
- Errors indicating that TMP Extras were not Imported logged when opening the Render Pipeline Converter Window while in Play Mode
Resolution Note (fix version 1.8.3):
Added dependencies to explicitly loaded catalogs that point to their local and remote hash locations. This feeds into DetermineIdToLoad in checking if the catalog has an updated version at the "remote" path.
This came with the need for an addition of a parameter to auto release the content catalog operation. If the handle isn't released when we re-load or check for catalog updates it'll still point towards the cached catalog location. The handle has to be released in order to load/update the secondary catalog.