Search Issue Tracker
Won't Fix
Under Consideration for 2022.3.X, 2023.2.X
Votes
0
Found in
2022.2.19f1
Issue ID
UUM-36049
Regression
No
Crash when building if “Build Addressables on Player Build” is set to “Build Addressables content on Player Build”
How to reproduce:
1. Open the user’s attached “kjenkins_DESKTOP-M26T9L2_SG_UnityUpgrade_6205.zip” project and connect it to Perforce
2. In the Project window, select “AddressableAssetSettings.asset”
3. In the Inspector window, change “Build Addressables on Player Build” to “Build Addressables content on Player Build”
4. Go to the Build Setting window and select the iOS platform
5. Build the project and observe the result
Expected result: No crash
Actual result: Crash
Reproducible with: 1.21.9 (2022.2.18f1), 1.21.10 (2022.2.18f1, 2023.1.0b15)
Could not test with: 2020.3.48f1, 2021.3.24f1, 2023.2.0a13 (Errors after project downgrade/upgrade)
Reproduced on: macOS 13.2.1 (Intel)
Notes:
Reproduced when building on iOS, but when building Standalone Player or Android then, the errors appeared
Not reproducible with “Build Addressables on Player Build” set to “Do not Build Addressables content on Player build”
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
- A new Additive Scene cannot be created when an empty Untitled Scene is not dirty
- [Scene View][Ubuntu] Prefab mode UI ghosting in HDRP
- Deleting AudioMixer asset throws MissingReferenceException and breaks the Audio Mixer window
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
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.