Skip to content

Conversation

@mikehardy
Copy link
Collaborator

Description

Attribute firestore GRPC calls to react-native language source

Related issues

Inspired by similar PR in FlutterFire sister project from @SelaseKay -

Release Summary

also includes a trivial firebase-ios-sdk bump, both are conventional commits and will release correctly automatically with no further attention

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

gl-rn language inclusion in x-goog-client-api header not directly tested but CI will show there is no regression in firestore functionality at minimum


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

@vercel
Copy link

vercel bot commented Oct 30, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
react-native-firebase Ready Ready Preview Comment Oct 30, 2025 6:03pm

…test

for some reason firebase-ios-sdk now returns the old session id even after
you set a tight expiration time and definitely wait for it to expire, skipping
for now. Android unaffected
@mikehardy mikehardy force-pushed the @mikehardy/firestore-client-language branch from 0f1862a to 4892043 Compare October 30, 2025 18:00
@mikehardy mikehardy merged commit 69a1210 into main Oct 30, 2025
20 of 21 checks passed
@mikehardy mikehardy deleted the @mikehardy/firestore-client-language branch October 30, 2025 21:05
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.

3 participants