Im using hockeyapp to get crash reports.
How can i understand at which class/method/line did my application crashed ?
To get the most use out of crash reports from HockeyApp, you should upload your dSYM symbol files to the site. This will give you fully symbolicated crash logs where it clearly states the file, method and line number where your crash is occurring.
For detailed instructions on how to do that, see this support article.
Some where you set/assign image as a parameter/argument. and this image is nil in case but this image should not be nil.
for example:
-(void)setImageOnExampleView:(UIImage*)image{
//if here is image = nil and if you call this method anywhere such crash will happen
[yourImageView setImage:image];
}
So, to detect where this crash occur, in possible places, where you are setting image; you should set "Break Point and debug in which classes of which method this crash occur.
Related
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.
Sample Iphone App Crash Report
Hi this is Symbolicating iPhone App Crash Reports image. I could not found where is crash so can u help me find crash
Use Symbolicatecrash tool, you can check the link to know how to use the tool to symbolicate your crash report.
As far as your crash is concern, it happened in thread 0 however to know exactly what went wrong in code, you need to symbolicate your crash because crash log is only showing addresses.
My Question is that : when and how often our Xcode produce crash logs?
reproduced steps as below:
1.Clear the log '~/Library/Logs/DiagnosticReports/' && '~/Library/Logs/CrashReporter/MobileDevice/' to make sure that all
history crash logs were removed from mac
Simulate one crash from project [e.g.: insert nil object to dic]
Check the path ~/Library/Logs/DiagnosticReports/
Result: I can't find the crash logs. [i tried device also ,get the same empty crash log]
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.
I have crash in my project. I use MKMapView and sometimes it crashes in addAnnotation(s) method.
I get message from XCode that crash stating
method _insert(objc_object*, MKQuadTrieNode*, MKQuadTrie*)
Please, help me.
please see the below image
P.S. Crash is reproduced not always. It is reproduced after 100+ annotations, sometimes after 300 or 500+. This objects are returns from server and I check coordinate for it.
Enable Zombies in your project.
Press CMD+< and select Enable Zombie Object in Diagnostic tab.
Now your are able to see what's wrong.
hope this help.