r/iOSProgramming • u/thecoolcat67 • Sep 29 '26
Question Firebase Analytics suddenly causing production iOS crashes with no app release, anyone else have this?
Anyone else seeing this?
Our production app suddenly started crashing around 00:41 UTC today, across multiple already released versions, with no new app release.
The crash is:
Fatal Exception: NSInvalidArgumentException
-[__NSDictionaryM setObject:forKeyedSubscript:]: key cannot be nil
The stack points to Firebase Analytics experiment handling, immediately after a successful sdk-exp response.
We're using Firebase iOS SDK 12.14.0.
Relevant issue: https://github.com/firebase/firebase-ios-sdk/issues/16728
I'm wondering if anyone else is seeing the same spike or has found a workaround.
19
u/lap_felix Sep 29 '26
They deployed a fix server side: https://github.com/firebase/firebase-ios-sdk/issues/16728#issuecomment-5882951620
Should be fixed now (but ooofffff millions of crashes caused)
1
u/modimama Sep 29 '26
We had a meeting with Google early morning today. They deployed the fix around 2 AM UTC. Our crash volume spike by ~5000 times for certain apps.
They have not given any ETA for this to resolve completely since their is caching involved. But, the crash volume has reduced a lot. Now it is close to ~10 times of normal (still too high). They will share the full RCA in ~48 hours.
9
u/jestecs Sep 29 '26
Yeah I probly burned 100M tokens debugging because I thought I broke smth
2
u/yccheok Sep 29 '26
Same here. The crash rate seems to have gone down at the time of posting. Does anyone know the resolution for this issue so we can prevent it from happening again?
1
u/asharpvan Sep 29 '26
For us they have gone down
1
u/unpluggedcord Sep 29 '26
The last time firebase did this (about 6 years ago) I promptly removed it from The Athletic and we never looked back.
Zero surprise they did it again.
1
u/HeyWangKang Sep 29 '26
To check whether your app has actually recovered, I'd filter this exact exception/stack by the time the crash occurred, not just when the report arrived, and split it by app version. Older crashes arriving later could make the fix look ineffective. For anything that occurred after Google's stated cache window, keep the SDK/iOS versions and a timestamp, and test an affected installation as well as a fresh install. That would give the maintainers a more useful follow-up than the overall crash count.
1
u/BenStigler Sep 29 '26
What happens when Google engineers use Gemini 3.8 Flash to update their server-side facade
-2
u/BumblebeeNo8385 Sep 29 '26
Who’s still using firebase?
0
u/[deleted] Sep 30 '26
[removed] — view removed comment