--
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/0e8a4035-5b93-4a6c-ad46-6f6cd9d71fae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Brad,After chatting this over with some of our Crash Reporting gurus, I think that you've got the gist.It looks like reporting caught exceptions is Android only at the moment due to some complexities in how iOS handles true native crashes.I'll make sure there's a feature request on the list for this. It wouldn't hurt to put in your vote by submitting a feature request (and linking to this thread) as well.☼, Kato
On Tue, Sep 6, 2016 at 9:20 AM, Brad McDermott <br...@touchlab.co> wrote:
From the docs it seems like only the custom logging is available on iOS, but not the ability to report caught exceptions as crashes without actually crashing the app.Is there some way of doing this currently on ios, or does anyone know if it will make its way to the iOS Firebase SDK at some point?
--
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/0e8a4035-5b93-4a6c-ad46-6f6cd9d71fae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.