Search Issue Tracker
Fixed in 2018.1.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
1
Found in
5.6.2p3
Issue ID
950637
Regression
No
[iOS] Call stack shows wrong information when exception/crash occurs on iOS devices
To reproduce:
1. Open project attached by the user
2. Build "Test" scene with IL2CPP backend for iOS device
3. Run built app on iOS device
Expected result: When an exception occurs it should point out which part of code caused the exception.
Actual result: After exception occurs call stack points to non-existing code.
Reproduced with: 5.5.0f3, 5.6.3p3, 2017.1.1p2, 2017.2.0b11, 2017.3.0a7
Device: iPad Mini 3 iOS 10.3.2
Not reproducible on Android platform with IL2CPP backend.
Fixed in: 2018.1.0a2
Backported to: 5.6.4p1,2017.1.2p1, 2017.2.0p2, 2017.3.0b7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The mouse cursor is positioned in the center when Cursor.LockState is set to CursorLockMode.Confined and changing the mouse position
- Undefined symbol errors appear when building Xcode project using BuildPipeline.BuildPlayer
- Building a Player fails when using special characters in “Product Name” field
- [VFXG] Clicking on Allow Instancing box resets exposed properties to default values
- [iOS] Unable to select streaming apps when using broadcasting on iOS device
Add comment