Crash Reporting Best Practices

[GThoma2]

I am implementing Firebase into an iOS app of mine and would like to utilize crash reporting. However, I am not very experienced in software development and do not know best practices when trying to catch errors. 

I was thinking of just sticking FIRCrashMessages within functions that are being called regularly. Is there a better method to observe crashes?

Thanks

[Kato Richardson]

Hi Thomas(?),

The getting started guide suggests that the best place to initialize your crash reporting is in `application:didFinishLaunchingWithOptions`. Once you have it enabled, the reports should be fairly automated.

I hope that helps!

☼, Kato

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/682c28e2-585d-46de-bb04-c90e9ae71bdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398

[GThoma2]

Cool, yeah I've done that and the reports seem to tell me exactly what's causing the crash. I didn't know if there were further steps I could/should take to achieve better crash logging before I deploy my app.

Thanks!

On Friday, February 24, 2017 at 12:49:20 PM UTC-6, Kato Richardson wrote:

Hi Thomas(?),

The getting started guide suggests that the best place to initialize your crash reporting is in `application:didFinishLaunchingWithOptions`. Once you have it enabled, the reports should be fairly automated.

I hope that helps!

☼, Kato

On Fri, Feb 24, 2017 at 9:00 AM, GThoma2 <galen.th...@gmail.com> wrote:

I am implementing Firebase into an iOS app of mine and would like to utilize crash reporting. However, I am not very experienced in software development and do not know best practices when trying to catch errors. 

I was thinking of just sticking FIRCrashMessages within functions that are being called regularly. Is there a better method to observe crashes?

Thanks

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/682c28e2-585d-46de-bb04-c90e9ae71bdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Doug Stevenson]

If you want, you can do better in your crash logs by using the logging API to add messages to the crash report.  This lets you can track things that happened up until the time of the crash.  Typically this isn't necessary, but for errors that are difficult to diagnose, it can be a big win.

https://firebase.google.com/docs/crash/ios#create_custom_logs

Doug