The two-line cleanup that crashed iOS apps on launch
On Monday evening, September 28, 2026, iPhone apps started crashing the moment people opened them. Not one app. Not a flaky update. App after app, open, crash, gone. If you were an iOS developer that night, your phone was a crime scene and your users were the witnesses. The first suspect was obvious. Apple had shipped iOS 27.0.1 that same day. A new OS release plus apps dying on launch is a story…
On September 28, 2026, iOS apps began crashing immediately upon being opened by users. This widespread issue, affecting numerous applications, became a major concern for developers and users alike. The first speculation was that the problem stemmed from the recent iOS 27.0.1 update, but developers soon identified a different culprit.
The root cause was traced back to a two-line change made on a server, unrelated to the operating system. This change, a cleanup of a legacy configuration flag in Google Analytics for Firebase, led to a malformed configuration payload being served to the SDK. When the SDK attempted to access a missing dictionary key, it triggered an NSInvalidArgumentException error, resulting in app crashes upon launch.
The change occurred at 17:38 Pacific time, causing the faulty configuration to roll out globally within three minutes. Despite the crash, the Firebase status dashboard remained green, as it relied on server-side metrics and did not reflect the client-side issue. Consequently, developers were unaware of the problem until crash alerts spiked and bug reports flooded GitHub.
The outage lasted for 2 hours and 11 minutes, highlighting the importance of monitoring not only server health but also client-side errors. The postmortem revealed that the existing tests had passed, as they did not account for the reference to a non-existent flag left behind by the removal of the stale configuration. This incident underscores the need for comprehensive testing that encompasses all potential failure points in the system.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
