Search Issue Tracker
Fixed
Fixed in 1.21.20, 2.0.3
Votes
0
Found in [Package]
1.21.19
Issue ID
ADDR-3623
Regression
No
The wait for completion workflow with “Addressables.LoadAssetsAsync“ fails and errors appear when using local bundles using web request
How to reproduce:
1. Open the user’s attached “WaitForCompleteError.zip” project
2. Go to the Addressables Groups window (Menu > Window > Asset Management > Addressables > Groups)
3. Press Build > New Build > Default Build Script
4. Enter Play Mode and observe the result
Expected result: A red cube is visible in the Game window, and no errors in the Console window
Actual result: The red cube is not visible in the Game window, and errors appear in the Console window
Reproducible with: 1.21.19 (2021.3.35f1, 2022.3.19f1, 2023.2.9f1)
Not reproducible with: 2.0.6 (2023.2.9f1, 2023.3.0b6)
Fixed in: 2.0.3 (2023.2.9f1)
Reproduced on: macOS 14.2.1 (Intel)
Not reproducible on: No other environment tested
Note: if testing the Completed callback, the cube is loaded successfully (user’s info)
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note (fix version 2.0.3):
Fixed in: 2.0.3
Resolution Note (fix version 1.21.20):
Fixed in: 1.21.20