Gergely Orosz on X: "Oh my god, Firebase’s SDK started to crash ALL iOS apps that were using it, for ALL sessions, just like that, no way for any of these apps to do anything… How amateur is all of this from any SDK, but especially one from a company with as high of an engineering bar like Google…" / X

Post

Gergely Orosz
@GergelyOrosz
Oh my god, Firebase’s SDK started to crash ALL iOS apps that were using it, for ALL sessions, just like that, no way for any of these apps to do anything… How amateur is all of this from any SDK, but especially one from a company with as high of an engineering bar like Google…
Vijay Tholpadi
@VijayTholpadi
9h
github.com/firebase/fireb… incase anyone has been wondering why their iOS apps are intermittently crashing since today morning 🙃 reminds me of the Facebook swizzling crash incident. @Firebase pls help
6:49 · 29 Sept 2026
263.6k
Views
88
Gergely Orosz
@GergelyOrosz
4h
Can you believe this: mobile devs sitting around seeing 100% of their app sessions crashing, unable to do anything, knowing the Firebase SDK/team screwed up, but that team itself doesn’t even know!! What is this, vibe coding? Eg 110K crashes:
6
Gergely Orosz
@GergelyOrosz
4h
Firebase made some server side change that stated to crash several versions of their SDK Again… how on earth do they make any change without validating it?? Their one job is to have the SDK work. If the SDK crashes Firebase has no business…
3
Gergely Orosz
@GergelyOrosz
4h
The GitHub issue tracker is begging Google to roll back the breaking, server-side change. I’m asking: how did it make it into prod, without validation, to start with?? Someone else asking: was this Gemini 🙃
2
Gergely Orosz
@GergelyOrosz
4h
Devs using the Firebase SDK are more competent than the Firebase team, in terms of incident management. Yes, this is what Firebase should do And yet, their status page shows no incident!! Even 5 hours later, here status.firebase.google.com 🤡 on the Firebase team - sorry but true
2
Gergely Orosz
@GergelyOrosz
4h
~100 messages later on the issue tracker, a Firebase dev FINALLY noticed How on earth did Firebase’s own monitoring not notice they broke all apps using them? That’s what I don’t get
1
Gergely Orosz
@GergelyOrosz
4h
Another dev confirms they’re looking into it:
1
Gergely Orosz
@GergelyOrosz
4h
Damn, DoorDash crashing, that will hurt their business (and push hungry customers to order with UberEats instead!) Why is DD using Firebase btw?
3
Gergely Orosz
@GergelyOrosz
3h
can-shaw: GREAT question. Given two Firebase devs confirmed Google knows it’s an incident, the Firebase status page should have been updated. But it’s not: so what is going on with incident management at Firebase? This is amateur category, again
3
Gergely Orosz
@GergelyOrosz
3h
AN HOUR LATER finally the server-side change crashing all iOS apps is rolled back But there’s no comms on the status page. No postmortem promise. For an incident this massive, neither is acceptable. How did this change go out? Why did validation not catch the break? What is
2
Gergely Orosz
@GergelyOrosz
3h
A 2 to 6 hour global outage… 6 hours for clients that cached the malformatted server payload. So so disappointing both how this could happen the first place with an SDK, one developed by Google, how devs had to alert Google. Will we get a postmortem at all?
3
Gergely Orosz
@GergelyOrosz
2h
I will write in depth about this, and sent questions to Google. I still cannot wrap my head around that 1) a backend change went out seemingly with zero verification (!!) 2) Firebase seemingly did not detect the outage 3) after confirming there's an outage, the status page is
1
Dmitrii Kovanikov
@ChShersh
3h
> Google > High engineering bar lol
3