Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2018.1.0a7
2018.1.6f1
Issue ID
1052529
Regression
No
[2018.1][Android][.NET 4.x][IL2CPP] StackTrace is not printed when .apk crashes
StackTraces are missing for exceptions when using IL2CPP and .NET 4.x runtime. By switching to .NET 3.5 runtime StackTraces are printed normally
To reproduce:
1. Download attached project "AndroidStacktraces.zip" and open in Unity
2. Open "SampleScene" scene
3. Set Android platform
4. Go to Player Settings > Other Settings and change Scripting Runtime Version to Stable (.NET 3.5 Equivalent) and set Scripting Backend to IL2CPP
5. Build and run the project on an Android device
6. Press "Crash" button and observe Stack trace is printed normally
7. Go to Player Settings > Other Settings and change Scripting Runtime Version to Stable (.NET 4.x Equivalent) and set Scripting Backend to IL2CPP
8. Build and run the project on an Android device
9. Press "Crash" button and observe that there is no Stack trace
Notes:
- Logcats are shared in the comments section
- This issue is reproducible only on Android devices
- This issue is not reproducible in iOS devices
- This issue is not reproducible in Windows and OSX Standalones
- This issue is not reproduced in Editor
Devices:
- Samsung Galaxy S9, OS: 8.0.0, CPU: arm64-v8a, GPU: Mali-G72 - Reproduced
- Google Pixel 2, OS: 8.1.0, CPU: arm64-v8a, GPU: Adreno (TM) 540 - Reproduced
- iPhone 7, iOS: 11.2.6, CPU: A10 - Not Reproduced
Reproduced on Unity 2018.1.0a7 and 2018.1.7f1
Not reproduced on Unity 2017.4.6f1, 2018.1.0a6 and 2018.2.0b10
Regression on Unity 2018.1.0a7
Could not check this issue on Unity 2018.3.0a3 because project becomes corrupted
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- A different Font Asset is applied when the original Font Asset is deleted while UI Builder is open
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
Add comment