Crashlytics Incident #20005
Missing crash reports in Firebase Crashlytics
Incident began at 2020-07-28 03:12 and ended at 2020-07-28 05:45 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Jul 28, 2020 | 05:45 | The issue with Firebase Crashlytics has been resolved for all affected projects as of Tuesday, 2020-07-28 05:44 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
|
| Jul 28, 2020 | 04:42 | Description: We've received a report of an issue with Firebase Crashlytics as of Tuesday, 2020-07-28 01:33 US/Pacific. Currently about 25% of crash reports are not being ingested correctly and will not be available for inspection. Our engineering team continues to investigate the issue. We will provide more information by Tuesday, 2020-07-28 05:45 US/Pacific. Diagnosis: Missing crash reports. Workaround: None at this time. |
|
| Jul 28, 2020 | 03:38 | Description: We've received a report of an issue with Firebase Crashlytics as of Tuesday, 2020-07-28 01:33 US/Pacific. About 50% of crash reports are not being ingested correctly and will not be available for inspection. Our engineering team continues to investigate the issue. We will provide more information by Tuesday, 2020-07-28 04:45 US/Pacific. We apologize to all who are affected by the disruption. Diagnosis: Missing crash reports. Workaround: None at this time. |