Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.21.19
2.0.8
Issue ID
ADDR-3631
Regression
No
Addressables.InstantiateAsync does not pass along the original exception chain when a dependency fails to load
How to reproduce:
1. Open the attached project "AddressablesBug.zip"
2. Open Window>Asset Management>Addressables>Groups
3. Click Build>New Build>Default Build Script in the Addressables Groups window
4. Change "Play Mode Script" to "Use Existing Build (Windows)"
5. Rename "defaultlocalgroup_assets_all" to "a" in Library\com.unity.addressables\aa\Windows\StandaloneWindows64
6. Enter Play Mode in the Editor
Expected results: InstantiateAsync exception is composed of 4 separately chained exceptions
Actual results: InstantiateAsync exception is composed of a single OperationException instead of the 4 separately chained exceptions
Reproducible with: 1.21.19 (2021.3.35f1, 2022.3.19f1, 2023.2.10f1), 2.0.8 (2023.2.10f1, 2023.3.0b7)
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.