- Home /
Crash logs from iOS device not helpful. Any Tips?
In a native app after it's released to the public, we could use something like QuincyKit to automatically send us crash logs. Besides the symbolication problem with Unity which can be solved with some flags when compiling the app, the crash logs from a Unity app are not really helpful.
Maybe I'm missing something, but I cannot know in which line of the script it crashed. I only get that there was an exception. Wow!! Where??? It's as helpful as a user telling you "it crashed!" Is there some workaround or is this a limitation of using Unity? I've seen some similar posts but no one answered them!
Can someone shed some light on this?
Don't forget that all your game script gets converted into arm assembler on build, so there is no such thing on the ios device as a script line number.
So there is absolutely no way to get some more info on the error? I know there is a Safe and Slow execution setting for the scripts but I don't think it gives more info on the script problem
I am also experiencing crashes on the device. Did you find a way to better understand what is the problem with your app?
I thought that Unity 4.2 iOS Crash Reporter would have solved this, but it just gives you the native iOS crash log. I guess this is only useful for Unity when they have some crash in their engine code.
Your answer
Follow this Question
Related Questions
Access Violation (0xc0000005) 0 Answers
Can you help me understand this iOS Crash Log? 0 Answers
Unity runtime crash when closed by windows task scheduler 0 Answers
Random crash in ntdll.dll 0 Answers
Editor Crash on Launch. 0 Answers