Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.30f1
Issue ID
UUM-49596
Regression
No
Addressables build fails when building embedded DLLs
How to reproduce:
1. Open the attached “addressable-build-issue.zip“ project
2. Open the Addressables Groups window (Window > Asset Management > Addressables > Groups)
3. Build Addressables (Build > New Build > Default Build Script)
Expected result: Addressables are built
Actual result: Addressables aren’t built and errors are thrown in the Console
Reproducible with: 1.12.15, 1.21.17 (2021.3.30f1), 1.21.17 (2022.2.19f1)
Not reproducible with: 1.21.17 (2022.2.20f1, 2022.3.9f1, 2023.1.13f1, 2023.3.0a5)
Can’t test with: 2023.2.0b9 (AR Foundation error in the Console)
Reproducible on: macOS 13.4.1 Ventura (Intel)
Not reproducible on: No other environment tested
Note: Addressables are built if the project is built first (creating a Build creates the PlayerData folder and a folder in the Temp/ directory that has all the DLLs and as long as Unity is not closed in the middle, the Addressables Builds succeed)
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
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.