Is that possible to complete a function(iOS Crash Follower) in the code for finding crash address or grasping the last called function in the callstack when app crashed?
With this function,we can easily to find out where the app crashed and then show crash information on the console, or maybe it can collect crash information before it feedback to us when mobile-net works.
Is anybody knows?
And give BugHD a try, iOS OSX & Android all supports, with very detail crash report.
Related
I have about 8 testflight internal testers for an app I'm developing, for crash reporting we are using Crittercism, some people see crashes that don't get reported to crittercism, why is that? how do I guarntee that all crashes get reported?
and if we read in this article in apple's documentation
However, crash logs are not sent to Apple unless the user agrees to
share crash data with app developers. TestFlight users automatically
agree to share crash data. The service does the following to generate
crash reports:
any hints ?
After experimentation, it looks like Firebase reports crashes in a way much better than Crittercism, and catches them all and provides better details.
and to quote bajracharyas353 :-
"crash reports were sent to us only on the next app launch on the
device where the app crashed."
my app crashed, and while i was relying on firebase crash report to get some answers; the stack trace just didn't make any sense to me.
this is what I was able to get from them, how can I make use of those numbers they offer me:
I have an app that works fine on simulator but when I run it on Ipad it crashes randomly. I am really in big trouble I have to submit the app tomorrow.
I cant understand the crash report, and the app is big I have 40 files, and many segues and http requests. its impossible tocheck on each file!
where to look?
does this hint on anything:
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x000000010014c164
Triggered by Thread: 0
Please guys any help will be great, am in big trouble!
Update:
the application has many api calls, after doing like 4 - 5 calls the app exit and stay in the background.
I can't know if its the actual issue, but I am guessing here because staying on the same page, the app won't crash.
what should I do guys?
It is a little hard to give you concrete help with this information.
I would suggest you add a crash report tool to your app (like Crashlytics).
That way you will get a readable report when an actual device crash and a will be more reasonable to fix.
It is a good practice to have a crash report tool in any production app.
We have used several 3rd party crash logs in past like crittercism, Flurry, crashlytics etc. There're some crash logs in which we are not able to get exact crash point. So, do we have any tool available which provides exact crash point ?
OR which is best 3rd party crash log tools in iOS ?
Depending on the type of crash, stack traces may not contain any of your apps code, which is perfectly fine.
Especially when dealing with memory issues, the crash will happen somewhere completely different than where the bug in your application is. You will have to check for the Exception Type information in the crash log and then go from there.
The following documents can help you understand crash reports better:
https://developer.apple.com/library/ios/technotes/tn2151/_index.html
http://www.raywenderlich.com/23704/demystifying-ios-application-crash-logs
You should also use the tools Xcode provides to make sure there are no easy to detect bugs by using the Instruments Leaks tool, use the Analyze build feature in Xcode, or the Address Sanitizer check in Xcode 7.
I know there are many crash reporting tools available in the market to collect crashes from the real devices. I would like to know how a crash reporting tool really collects its data?. Does it collect a crash report from the operating system once the crashed application launched again? or Does iOS allows the crash reporter to collect the data as soon as the app is crashed?.
It will be really great if somebody can explain what happens after an app is crashed or point me to right place.
System crash logs are located at /private/var/mobile/Library/Logs/CrashReporter/ and (as far as I know) can't be accessed by the app directly. Most crash reporting tools will try to catch crashes and generate their own crash reports which will get stored locally and sent to a server for symbolication and processing.
You can take a look at the source for KSCrash, an open source crash reporting tool, to see how crashes are caught/stored/reported.