Crash in nanopb iOS 17.4.0

Question

My app started crashing right on startup on iOS 17.4. Prior this version everything was ok. Crashlytics says this is some crash in nanopb on main thread in pb_check_proto3_default_value + 342.

Crashed: com.apple.main-thread
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x00000001736eb51c

As you can see, right in AppDelegate, Firebase starts its warming up routines (I guess) and crashes.

nanopb sources are cryptic for me because I don't know C. The worst part the bug is reproducible only in Testflight builds, local builds (both release and debug) work well.

What can I do, guys? Maybe some of you experienced this problem on iOS 17.4 as well?

Geoffrey

Possibly related: github.com/firebase/flutterfire/issues/12442 – Valkyrie

Answer 1

This is a bug in Firebase, which should be fixed in version 10.22.0.

https://github.com/firebase/firebase-ios-sdk/issues/11403

Valkyrie

I was using CocoaPods and I had Firebase Crashlytics 10.20.0. Updating pod using pod update FirebaseCrashlytics to 10.22.0 fixed the issue. – Zipangu

I have had nanopb: safe_read_bool and I believe this one fixed it. Thank you so much for the help, @Valkyrie have a great day!!! – Iatry

I'm still running React Native v0.67.5 - can't seem to upgrade react-native-firebase.. am I fucked? – Treed

Answer 2

In addition to jpa's answer of updating to Firebase 10.22.0, you can stick with Xcode 15.2 or earlier for previous Firebase versions.

The Xcode 15.3 release mode build exposes/introduces the coding issue in FirebaseSessions.

Yamamoto

Answer 3

Update the firebase version. If you use spm update it from spm manager or cocoapods, update it as pod install --repo-update. It should fix the issue.

Apostolate

Answer 4

I was getting this error while installing ipa file. same build was working when running from xcode. also, this works in iOS 16, issue is only in iOS 17. this issue can not trash with firebase crashlytics as well. because app will crash before it launch completely.

to fix this issue, just update firebase pod like this, and it will work.

pod update Firebase

Mattos