A server-side change from Firebase triggered a widespread runtime failure in iOS apps using its SDK, causing crashes across essentially every user session and generating reports on the order of 110,000 crashes. Developers found their apps repeatedly crashing with no way for users to proceed, and major customers like DoorDash were affected. Some clients that had cached a malformed server payload experienced extended outages - reports say the impact lasted from two to six hours for those installations - until Firebase rolled the change back roughly an hour after the problem was first flagged.
The response drew sharp criticism: developers discovered and raised the issue via a GitHub thread while Firebase’s public status page showed no incident, and the Firebase team reportedly didn’t detect the break through their own monitoring initially. Commenters compared it to earlier SDK swizzling accidents and questioned how a company of Google’s engineering reputation could push an unvalidated server change that broke shipped SDKs. Calls for clearer incident comms, a prompt rollback, and a formal postmortem were repeated across the thread, with many saying third‑party developers managed the incident better than the SDK provider did.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.