April 17, 2017
Score 10 out of 10
Overall Satisfaction with Crashlytics
We are using Crashlytics to track both fatal and non-fatal errors that occur in both our iOS and Android native mobile apps.
- Pulling the stack trace from an error
- Bundling errors of the same kind across multiple versions
- Allowing for caught Exceptions to also be reported as non-fatal errors
- Would be great if they could link common system-level exceptions to solutions
- Sometimes the stack trace is not entirely useful, but not sure what can be done in those scenarios
- We've been able to track down the root cause of an issue that we were not experiencing during development or testing because it only occurs in certain cases of flaky connectivity. Even after identifying the cause, it was not a reproducible issue, but because we are able to log non-fatal errors also, we could verify that the fix was working in production.
BuddyBuild's crash reporting tool is a far cry from Crashlytics, and the interface is also not nearly as good.