Search Issue Tracker
Fixed
Fixed in 2021.3.17f1, 2022.2.2f1, 2023.1.0a20
Votes
1
Found in
2021.3.11f1
2022.1.19f1
2022.2.0b10
2023.1.0a13
Issue ID
UUM-16259
Regression
Yes
[iOS] Player crashes on iOS 16 devices when “UnityFramework.framework” is added in “Link Binary With Libraries”
How to reproduce:
1. Open the user’s attached project
2. Go to Project Settings and build a project for the iOS platform
3. In Xcode go to the Build Phases tab and open “Link Binary With Libraries”
4. Press + and add “UnityFramework.framework”
5. Build an application to an iOS 16 device and observe the result
Expected result: No crash
Actual result: Crash and “Thread 1: EXC_BREAKPOINT (code=1, subcode=0x105bd5630)” error appears
Reproducible with: 2021.2.0a2, 2021.3.11f1, 2022.1.19f1, 2022.2.0b10, 2023.1.0a13
Not reproducible with: 2020.3.40f1, 2021.1.0a10, 2021.1.28f1
Could not test with: 2021.2.0a1 (Errors after project downgrade)
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.0 iOS repro
Not reproduced on:
VLNQA00358 - iPhone 12, 14.1 iOS no repro
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS no repro
VLNQA00392 - iPad (9th generation), 15.0 iOS no repro
Note: Not reproducible without the 3rd and 4th step
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 2023.1.0a20):
Fixed in: 2023.1.0a20
Resolution Note (fix version 2022.2.2f1):
Fixed in: 2022.2.2f1
Resolution Note (fix version 2021.3.17f1):
Fixed in: 2021.3.17f1