🚨Firebase SDK Crash Hits 110K iOS Sessions
Firebase's iOS SDK crash hits 110K users
TL;DR
Firebase's iOS SDK crashed all sessions for 110K users, causing a global outage. The incident lasted 2-6 hours and was rolled back without communication.
Firebase's iOS SDK crashed all sessions for 110K users, causing a global outage. The incident, reminiscent of the Facebook swizzling crash, was due to a server-side change made without proper validation. The Firebase team was criticized for not detecting the outage and not providing a postmortem. The crash affected all sessions, with no way for apps to function, and was rolled back after an hour. The incident highlights the need for better validation and communication practices in large-scale SDK deployments.
Key Points
Firebase SDK crash affected 110K iOS sessions, causing a global outage.
The incident lasted 2-6 hours, impacting all sessions without warning.
Firebase team rolled back the change after an hour without user communication.
The crash was caused by a server-side change made without validation.
The incident was compared to amateur coding practices and Facebook swizzling.
Why It Matters
If you're using Firebase in your iOS app, this outage highlights the importance of robust validation and communication practices. The crash affected all sessions, impacting 110K users globally. The lack of a postmortem or user communication from Firebase raises concerns about their engineering standards and incident response.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,518 builders reading daily.