Skip to content

fix(tests): bump FirebaseFirestore Podfile pin to 12.17.0 - #692

Open
demolaf wants to merge 4 commits into
mainfrom
fix/podfile-firestore-pin
Open

fix(tests): bump FirebaseFirestore Podfile pin to 12.17.0#692
demolaf wants to merge 4 commits into
mainfrom
fix/podfile-firestore-pin

Conversation

@demolaf

@demolaf demolaf commented Sep 14, 2026

Copy link
Copy Markdown
Member

The tests/ios and tests/macos Podfiles pin FirebaseFirestore to the invertase/firestore-ios-sdk-frameworks fork tag 12.15.0, last bumped in #663 back in July. Since then the resolved cloud_firestore plugin version now requires Firebase/Firestore 12.17.0, which conflicts with the stale pin and fails pod install with a CocoaPods resolver error on every e2e run, on main and on every open PR regardless of what it actually changes.

This bumps both Podfile pins to 12.17.0, which exists in the fork repo and matches what cloud_firestore currently resolves to.

The tests/ios and tests/macos Podfiles pinned FirebaseFirestore to the
invertase/firestore-ios-sdk-frameworks fork tag 12.15.0, last bumped in
#663. The resolved cloud_firestore plugin now requires
Firebase/Firestore 12.17.0, which conflicts with the stale pin and
fails pod install with a CocoaPods resolver error on every e2e run.

CPRN-450

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the FirebaseFirestore pod dependency version from 12.15.0 to 12.17.0 in both the iOS and macOS Podfiles. I have no feedback to provide.

12.17.0 was already stale by the time CI ran: cloud_firestore's
unpinned ^6.6.0 constraint resolved to 6.9.0 in this run, which
requires Firebase/Firestore 12.18.0.

CPRN-450
The tests app pinned org.jetbrains.kotlin.android to 2.1.0, but the
transitively-resolved firebase-auth Android AAR (24.2.0, pulled in via
the unpinned firebase_auth dependency) is compiled with Kotlin 2.3.0
metadata, which 2.1.0 cannot read:

  Module was compiled with an incompatible version of Kotlin. The
  binary version of its metadata is 2.3.0, expected version is 2.1.0.

Same class of drift as the FirebaseFirestore Podfile pin, just on
Android: an unpinned Firebase dependency moved ahead of a hardcoded
version elsewhere in the test app.

CPRN-450
Removes the caret ranges on firebase_auth, firebase_core, and
cloud_firestore in tests/pubspec.yaml, replacing them with the exact
versions currently resolved (firebase_auth 6.6.1, firebase_core
4.14.0, cloud_firestore 6.9.0).

These three drive the native-side Firebase SDK version through
firebase_core's FirebaseSDKVersion default (34.18.0 Android BOM,
12.18.0 iOS Firebase SDK), which is exactly what the tests/ios and
tests/macos Podfile FirebaseFirestore tag and the Kotlin Gradle
plugin version have to match. Left floating, any of the three can
silently resolve to a newer version on any CI run and break e2e on
a completely unrelated PR, which is what happened twice on this
branch already.

Everything else in the workspace stays unpinned, so the publishable
firebase_ui_* packages keep testing against the latest compatible
Firebase releases.

CPRN-450
@demolaf
demolaf added this pull request to stack #694 September 14, 2026 12:02

@russellwheatley russellwheatley left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean CI-unblock, pins match what's actually resolving. LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants