Crashlytics fatal crash storage limit

820 views
Skip to first unread message

Sarthak Agarwal

unread,
May 11, 2020, 8:22:03 AM5/11/20
to Firebase Google Group

Hi firebase team,

We are working on integrating crashlytics into our Android application
Our application needs support for long-term offline storage since our users may not be connected to the internet for weeks or months together.
We noticed that while crashlytics stores 8 custom events, fatal crashes in crashlytics do not have any storage limits (none that we could find in the documentation or in the persistEvent function
However we wanted to check with the team if that really is the case. Can we assume that crashlytics will store all of our crashes until the device is connected to the network once again (Given that the device may not be connected to the internet for a long period of time - like say few months)?

Kato Richardson

unread,
May 11, 2020, 12:07:02 PM5/11/20
to Firebase Google Group
Hi Sarthak,

Months is probably out of the question and not a use case we've designed for. I'm not sure what the limits are, but we'd obviously be limited by local storage at some point. So if an app is crashing regularly, it would certainly run out of storage space.

On the flip side: Assuming a consumer oriented user base, I doubt anyone offline for several months would endure that many crashes without leaving the app; you won't be able to respond to these quickly enough to keep them engaged.

☼, 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-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/188b8a97-ec6b-40c9-91b1-d4dedb1554ff%40googlegroups.com.


--

Kato Richardson | Developer Programs Eng | kato...@google.com | 775-235-8398

Todd Burner

unread,
May 12, 2020, 12:48:22 PM5/12/20
to Kato Richardson, Firebase Google Group
Hi folks,

There are a few things here:

1 - Crashlytics only shows 90 days of data.
2 - If the timestamp is older than a week we change the timestamp to when it is processed.
3 - Crashes older than 3 days only get processed in our batch processing which means they can take almost 24 hours to appear after the device uploads them.
4 - Crashlytics will only hold something like 12 crash reports, after that it pushes out the least recent one to store a new one.

Thanks!
--
Google Logo
Todd Burner
Developer Advocate - Firebase
tbu...@google.com
Reply all
Reply to author
Forward
0 new messages