Crashlytics Incident #19004
Delayed crash reports on Firebase Crashlytics.
Incident began at 2019-06-03 13:10 and ended at 2019-06-03 13:50 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Jun 03, 2019 | 13:50 | The issue with delayed crash reports on Firebase Crashlytics has been resolved for all affected users as of Monday, 2019-06-03 13:46 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence. |
|
| Jun 03, 2019 | 13:23 | We are experiencing an issue with customers seeing delayed crash reports on Firebase Crashlytics beginning at Monday, 2019-06-03 12:57 US/Pacific. Affected customers onboarding new products and/or forcing crashes might see delay for their crashes to appear on the dashboard. For everyone who is affected, we apologize for the disruption. We will provide an update by Monday, 2019-06-03 14:30 US/Pacific with current details. |
|
| Jun 03, 2019 | 13:10 | We are investigating an issue with Firebase Crashlytics. We will provide more information by Monday, 2019-06-03 13:45 US/Pacific. |