feat!: bump firebase-ios-sdk to 12.0.0

[russellwheatley]

Description

trackingId has been removed from firebase-ios-sdk: https://firebase.google.com/support/release-notes/ios#version_1200_-_july_15_2025

I've kept the gaTrackingId API in the JS code because it appears android still uses it: https://firebase.google.com/docs/reference/android/com/google/firebase/FirebaseOptions?_gl=1*dtmd6b*_up*MQ..*_ga*MzIzOTI0NDg4LjE3NTM5NjIwMjM.*_ga_CW55HF8NVT*czE3NTM5NjQxOTMkbzIkZzAkdDE3NTM5NjQxOTMkajYwJGwwJGgw#gaTrackingId()

Although we could possibly update it to match firebase-js-sdk which would be measurementId?

Related issues

Release Summary

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • Yes
• My change supports the following platforms;
  • Android
  • iOS
  • Other (macOS, web)
• My change includes tests;
  • e2e tests added or updated in packages/\*\*/e2e
  • jest tests added or updated in packages/\*\*/__tests__
• I have updated TypeScript types that are affected by my change.
• This is a breaking change;
  • Yes
  • No

Test Plan

---

Think react-native-firebase is great? Please consider supporting the project with any of the below:

• 👉 Star this repo on GitHub ⭐️
• 👉 Follow React Native Firebase and Invertase on Twitter

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-native-firebase	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 4, 2025 3:17pm

[mikehardy]

as long as we're breaking I think truing up the API to measurement vs tracking ID makes sense - we don't get frequent chances to clear out cruft, let's clear it out

That may imply that people need to download new a new set of plist/json firebase config files if theirs are really old I think...unsure

[russellwheatley]

I think all that is left to do is to add:

BREAKING CHANGE: iOS mininum target now 15.0, was 13.0

to commit body when merging.

[russellwheatley]

as long as we're breaking I think truing up the API to measurement vs tracking ID makes sense - we don't get frequent chances to clear out cruft, let's clear it out

That may imply that people need to download new a new set of plist/json firebase config files if theirs are really old I think...unsure

I don't think that will be necessary, ios release notes suggest it wasn't used/obsolete so I think having that property in plist will just be unused. I had a look at service info plist from 8 years ago and don't see analytics ID: https://github.com/invertase/react-native-firebase/blob/9308994db23b3d1acf903f94f12e0b2eabe84807/tests/ios/GoogleService-Info.plist so don't think it's ever been part of the downloaded service file.

[mikehardy]

I think I've got this one all rebased correctly to fix up conflicts

Looks good to go, excellent