Search Issue Tracker
Won't Fix
Votes
1
Found in
5.6.1f1
Issue ID
938457
Regression
Yes
[Android] [IL2CPP] Stack frames doesn't have any symbolic information in the backtrace (libil2cpp.so)
Steps to reproduce:
1) Download attached project and open in Unity
2) Make sure Scripting Backend is set to IL2CPP in Player Settings
3) Build and Run project on a device
4) Press the 'Crash repro' button
Observe the logcat. There is no symbolic information for libil2cpp.so in the backtrace
Expected result: In Development build there should be symbolic information for libil2cpp.so (check attached image 'SymbolicInformation5.5.png')
Actual result: There is no symbolic information for libil2cpp.so (check attached image 'SymbolicInformation5.6.png')
Reproduced with:
5.6.1p1, 5.6.3f1, 2017.1.0p3
Not reproduced with:
5.5.4p2
Device under testing:
Google Pixel*, OS:7.1.2, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:google/sailfish/sailfish:7.1.2/NJH47D/4045516:user/release-keys
Note: I wasn't able to check with 2017.2.x and 2017.3.x because this crash is fixed in those versions of Unity
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note:
We are struggling to get the build size down, and this request goes completely against that. We also don't provide function names for release libunity.so. For symbolicating callstacks, please use the archive with the symbols we leave next to the APK or use the latest services to get your crash info.