Firebase’s Scandalous Behavior with Xcode 15.3: A Never-Ending Crash Cycle 🚨

TL;DR: Developers using Firebase with Xcode 15.3 have been facing app crashes since early 2024. The issue affects Firebase services like Crashlytics and Analytics, leading to crashes on launch for many apps, especially on iOS 17.x. Despite multiple Firebase SDK updates (10.28 and 10.29), the problem persists. Temporary fixes like downgrading to Xcode 15.2 or disabling Firebase services are currently the best options.

What Happened?

In March 2024, developers started reporting crashes when using Firebase with Xcode 15.3. The crashes occur particularly during the initialization of Firebase services like Crashlytics and Analytics. The root of the issue seems to be in the FirebaseApp.configure() function, which leads to EXC_BAD_ACCESS errors, especially on devices running iOS 17.x.

Developers across Reddit, GitHub, and Apple Developer Forums quickly raised the alarm. One developer on GitHub explained:

"It crashed every time when I run code in Xcode 15.3. I just init Firebase, and it crashed. I run the app on my iPhone 13 Pro (iOS 17.4), not a simulator." [Source: GitHub issue #12989]​:contentReference[oaicite:0]0

Another user on Reddit described their frustration:

"It crashes 100% of the time when launching with Firebase on Xcode 15.3. Downgrading Xcode was the only solution that worked for me."

The problem is widespread and persistent, affecting apps that rely on Firebase for logging, analytics, and crash reporting.

How Users Reacted

Faced with these crashes, developers took matters into their own hands. Here’s what they’ve been doing to cope:

1. Downgrading Xcode

Many developers have reverted to Xcode 15.2 or even earlier versions to avoid the crashes. A user on Apple Developer Forums shared:

"Thanks, it is working fine with Xcode 14.3.1 and there is no problem now." [Source: Apple Developer Forums]​:contentReference[oaicite:1]1

This workaround seems to be the most reliable solution for now, albeit not an ideal long-term fix.

2. Disabling Firebase Features

To prevent crashes, some developers have opted to disable key Firebase services like Crashlytics and Analytics. While this prevents the app from crashing, it also limits the insights and data collection:

"We had to temporarily disable Firebase Analytics and Crashlytics to avoid these crashes. Not ideal, but it works for now."

3. Waiting for a Fix

Despite months of complaints, Firebase has yet to release a fix. Firebase SDK versions 10.28 and 10.29 introduced other improvements, but they didn’t address the Xcode 15.3 crashes.

On GitHub, a developer summed up the community’s frustration:

"It's been months, and Firebase hasn’t done much to address this. We're stuck downgrading or turning off Firebase services to keep our apps running." [Source: GitHub issue #12510]​:contentReference[oaicite:2]2

The iOS 11 and iOS 12 Factor

Another important issue revolves around iOS 11 support. Since Firebase SDK version 10.x, support for iOS 11 has been dropped, making the situation even more frustrating for developers targeting older devices. Firebase 10.x and above only support iOS 12 and later, forcing developers with legacy apps to either stick with Firebase 9.x or abandon iOS 11 support altogether.

For apps targeting iOS 11, you should stick to Firebase SDK 9.x versions or earlier. Trying to use Firebase 10.x will result in build failures or runtime issues.

What’s Going On Now?

As of September 2024, developers are still dealing with Xcode 15.3 crashes when using Firebase, despite multiple updates to the SDK. The issue remains unresolved in Firebase 10.28 and 10.29, leaving many apps vulnerable to crashes.

On GitHub, the conversation continues, with no clear timeline from Firebase on when (or if) this will be fixed. Developers are left with few options other than to wait or apply temporary workarounds.

What You Can Do For Now 🚒

While waiting for Firebase to release a permanent solution, here are some workarounds that may help:

1. Downgrade to Xcode 15.2

This is the most effective solution for now. Many developers have found that reverting to Xcode 15.2 or earlier versions eliminates the crashes. It’s not an ideal solution, but it’s currently the most reliable.

2. Disable Firebase Services

If downgrading isn’t possible, you can disable Firebase services like Crashlytics and Analytics to reduce the likelihood of crashing. This may result in loss of data or insights, but it will keep your app running.

3. Monitor Firebase Updates

Keep an eye on Firebase’s GitHub and Developer Forums for any announcements regarding a fix. The Firebase team is aware of the issue, but no clear solution has been provided yet.

Final Thoughts

The ongoing issue with Firebase and Xcode 15.3 is a cautionary tale of poor communication and slow response times. While developers scramble to find workarounds, Firebase has been slow to provide a proper fix.

Whether you downgrade Xcode, disable Firebase services, or just wait it out, the community continues to search for answers as the issue drags on. Hopefully, Firebase will release a comprehensive fix soon, but for now, we remain in a waiting game.

In the meantime, hang in there—and maybe grab a coffee while you wait for your app to crash. ☕