Search Issue Tracker
Fixed
Fixed in 2021.3.28f1, 2022.3.2f1, 2023.1.0f1, 2023.2.0a17
Votes
3
Found in
2020.3.42f1
2021.3.15f1
2022.1.24f1
2022.2.1f1
2022.3.1f1
2023.1.0a22
2023.2.0a1
Issue ID
UUM-20838
Regression
No
[iOS] “Application.lowMemory” callback is not invoked on iOS devices when a memory overflow occurs if using Unity as a Library embedded into a native Swift iOS application
How to reproduce:
1. Build And Run the user’s attached project on an iOS device
2. Open the app and wait for some time (30-60s)
3. Observe the result
Expected result: No crash
Actual result: App crashes and a message “warning: could not execute support code to read Objective-C class data in the process. This may reduce the quality of type information available.” appears
Reproducible with: 2020.3.42f1, 2021.3.15f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a22
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.0.3 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Not reproducible on:
VLNQA00472 - Samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2023.2.0a17):
Fixed in: 2023.2.0a17
Resolution Note (fix version 2023.1.0f1):
Fixed in: 2023.1.0f1
Resolution Note (fix version 2022.3.2f1):
Fixed in: 2022.3.2f1
Resolution Note (fix version 2021.3.28f1):
Fixed in: 2021.3.28f1