I am having trouble trying to understand what went wrong when my app crashed for a user based on a crash report i received back.
In Xcode organizer I can see the following:
I can open the crash report in project but all I get is:
This part doesn't change if I select any individual thread, I can't see any variables and it doesn't even tell me what line of code the thread was suspended at. Does anyone have any suggestions of how I should continue to debug this? Thanks in advance.
First of all this crash report is not symbolicated. You should do that. Xcode would do that for you if you download the crash report by Organizer.
Second, this exception usually occurs if you the index specified in objectAtIndex is too large. So if you don't have access to symbolication for this crash report then all you could do is to check all your objectAtIndex: calls to see if the index could get outside of the bounds.
Related
For a certain crash I am only getting TestFlight feedback and not the crash log. Meaning I cannot open the crash in Xcode to figure out what the issue is. Is there a reason for this?
How can I get the crash log?
I got a crash in my test flight version of an iOS application, but when I check the Xcode crash log system, I am getting the crashed line and crashed function name. But I was not able to find the reason of crash. Does anybody know how to find out the reason of the crash occurred?
Here is the screenshot of the crash log of Xcode -> Organiser.
From this I am not getting the crash reason.
There is a way to show the report in Finder, as per https://help.apple.com/xcode/mac/11.4/index.html?localePath=en.lproj#/devc8ced2ea3 by Control+Clicking in the list of crash reports on the left.
Please update your question with the .crash file, which should provide full information about the crash.
The function that actually crashed is objc_msgSend. The most likely cause is that you sent a message to an object that had a different type than you and the compiler expected.
My game in the appstore crashes from time to time. I get these crash reports from the Crashes Organizer. They are partially symbolicated. The problem is that the part where it's not symbolicated is the part I need to understand the most. How can I make sense of the address (0x100054000) in this crash log?
I tried to fix some bugs of my already distributed App, which I noticed through Apples crash report service, using the xCode Organizer (xCode -> Organizer -> Crashes). It's working fine and I'm able to open the crash report in my project, so xCode is showing me every detail of the crash like the line in my code, where the exception occurs, call stack, etc.
My problem is, that I can't find the exception reason like for example:
-[__NSArray0 addObject:]: unrecognized selector sent to instance 0x7fa99b801c40
which I need, to 100% identify the reason, why my App crashed on some devices at this line. I already studied Apple's article about Analyzing Crash Reports but without success.
Does anybody know, where I can see the reason of a crash in a crash report provided by Apple's Crash Report Service?
Right click on the crash report entry in Xcode's Organizer window and select "Show in Finder"
Right click on the revealed .xccrashpoint file in Finder and select "Show Package Contents"
Navigate to the DistributionInfos/all/Logs/<date-and-uuid>.crash subfolder within the .xccrashpoint file
Open the .crash file in Console.app
This will have the exception type and reason printed alongside the symbolicated stack trace
On OSX developers can provide an annotation before an app (possibly) crashes using the global __crashreporter_info__ declared like this to be accessible.
const char *__crashreporter_info__ = NULL;
asm(".desc ___crashreporter_info__, 0x10");
Unfortunately this seems not to be supported on iOS.
#bbum: Is there any way on iOS to annotate crash reports?
I have an app which is written in swift and uses AFNetwork and some other helpers written in Obj c. On my clients device (iPhone 6+) he is getting an SIGTRAP error, I have tried to recreate the issue on the testing devices that we have and on all the simulators but could not recreate it.
Below is the stack trace, it crashed twice:
http://paste.ubuntu.com/12077304/
When I symbolicate the crash report it is pointing to:
-[Instagram getOwnBaseUrl] (in DiaryApp) (Instagram.m:118)
And on the second instance it point to:
[UIAlertView(AFNetworking) showAlertViewForTaskWithErrorOnCompletion:delegate:cancelButtonTitle:otherButtonTitles:]_block_invoke (in DiaryApp) (UIAlertView+AFNetworking.m:72)
Crash Log : http://paste.ubuntu.com/12077328/
I am not able to pin point the exact cause for the crash. Any help in this regard will be highly appreciated.
Thanks.
SIGTRAP is not the error it is the exception. It doesn't show the origin of the crash. This exceptions throw into Main thread on Main/Next Runloop, so the stacktrace of the main thread does not show the origin of it.
It happen like NSArray indexOutOfBounds or library or anything else
reference link
signal Types