Search Issue Tracker
Fixed in 1.19.4
Votes
0
Found in [Package]
1.18.19
Issue ID
1395176
Regression
No
Addressables.InitializeAsync() handle is auto-released and false cannot be passed because the API is not exposed
Reproduction steps:
1. Open the user's attached project "Addr11819.zip"
2. Open PrefabsLoader.cs and change line 28 to "initOperation = Addressables.InitializeAsync(false);", save the change
3. Return to the Editor
4. Enter Play mode
Expected result: "Addressables library is initialized." is logged in the Console window after step 4
Actual result: Error "No overload for method 'InitializeAsync' takes 1 arguments" is thrown after step 3
Reproducible with: 1.17.17 (2020.3.31f1), 1.18.19 (2019.4.36f1, 2020.3.31f1)
Not reproducible with: 1.19.4 (2019.4.36f1, 2020.3.31f1), 1.19.19 (2019.4.36f1, 2020.3.31f1, 2021.2.15f1, 2021.2.0b11, 2022.2.0a8)
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 1.19.4):
Fixed in: 1.19.4 (Unity 2019.4.0f1 and above)