🔥 [🐛] missing ga_session_id on part of iOS Analytics events since upgrading to v23.8.3
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- ios, react-native, typescript
Research direction
Start with the Analytics version details in package.json and the Firebase versions in ios/Podfile, then inspect initialization in AppDelegate.m. Compare events from normal launches with events associated with background launches, especially session_start and ga_session_id. Done means identifying a reproducible cause or confirmed regression and verifying that affected iOS sessions report both values consistently.
Written by the indexing model from the issue text.
Description
Issue
Hello team,
Since upgrading @react-native-firebase to v23.8.3 (Firebase iOS SDK 12.8.0), on iOS, we are seeing a significant number (~4%) of Analytics events with a missing ga_session_id in production. This was present on the previous version but on a much smaller scale (~0.3%), and the upgrade is the only change correlated with the regression.
After inspecting GA4 events grouped by device, it appears that whenever this issue occurs, all events for the affected session are missing ga_session_id. We also noticed that the session_start event, which would normally precede the rest of the session's events, is also missing. Events from the same device begin reporting a valid ga_session_id again only after the session is recreated (e.g., the app is restarted after 30min).
This behaviour is consistent across all iOS versions we've analyzed (iOS 16 through iOS 26).
We suspect the cause may be related to background launches (e.g. triggered by silent push notifications). However, we were not able to reproduce this issue at all in development.
Thank you very much for the support
Project Files
Javascript
Click To Expand
package.json:
package.json:
{
"@react-native-firebase/analytics": "23.8.8",
"@react-native-firebase/app": "23.8.8",
"@react-native-firebase/crashlytics": "23.8.8",
"@react-native-firebase/installations": "23.8.8",
"@react-native-firebase/remote-config": "23.8.8",
"react-native": "0.81.6"
}
iOS
Click To Expand
ios/Podfile:
- I'm not using Pods
- I'm using Pods and my Podfile looks like:
use_frameworks! :linkage => :static
$RNFirebaseAsStaticFramework = true
target 'XXXX' do
pod 'FirebaseMessaging', '12.10.0'
end
AppDelegate.m:
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions{
...
[FIRApp configure];
....
}
Android
Not investigated; issue observed on iOS only.
Environment
Click To Expand
react-native info output:
System:
OS: macOS 26.5.2
CPU: (12) arm64 Apple M3 Pro
Binaries:
Node: 20.19.4
CocoaPods: 1.16.2
npmPackages:
react: 19.1.4
react-native: 0.81.6
iOS:
hermesEnabled: true
newArchEnabled: true
- Platform that you're experiencing the issue on:
- iOS
- Android
- iOS but have not tested behavior on Android
- Android but have not tested behavior on iOS
- Both
react-native-firebaseversion you're using that has this issue:- initially seen in 23.8.3, now on 23.8.8 with same issue
Firebasemodule(s) you're using that has the issue:- @react-native-firebase/analytics, @react-native-firebase/crashlytics
- Are you using
TypeScript?- Y & 5.8
- Dominant language
- TypeScript
- Stars
- 12.3k
- Forks
- 2.3k
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 32
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from invertase/react-native-firebase
-
Needs Attention type: bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
invertase/react-native-firebase#9354 · 1 comment ·
Maintainers usually reply within 1 day
-
Needs Attention type: bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
invertase/react-native-firebase#9349 ·
Maintainers usually reply within 1 day
-
platform: android platform: javascript plugin: database type: bug
Difficulty 5/5 Over a week Newbie friendliness 35/100
invertase/react-native-firebase#9344 · 1 comment ·
Maintainers usually reply within 1 day
-
platform: ios plugin: database type: bug
Difficulty 3/5 1-2 days Newbie friendliness 78/100
invertase/react-native-firebase#9339 · 3 comments ·
Maintainers usually reply within 1 day
-
blocked: customer-response platform: android plugin: app-check Stale type: bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
invertase/react-native-firebase#9227 · 7 comments ·
Maintainers usually reply within 1 day
All issues in invertase/react-native-firebase
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
callstackincubator/rozenite#518 ·
Maintainers usually reply within 1 day
-
Area/Workflow Priority/Blocker Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
wso2/product-integrator#2622 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area:bash bug has repro platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anthropics/claude-code#98644 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
allure-framework/allure-js#1603 ·
Maintainers usually reply within 1 day