Repository navigation
fix(analytics): pause the launch session when the client is created in the background - #3500
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3500 +/- ##
==========================================
+ Coverage 57.77% 57.81% +0.03%
==========================================
Files 1129 1129
Lines 33268 33281 +13
Branches 4961 4965 +4
==========================================
+ Hits 19222 19240 +18
+ Misses 12117 12112 -5
Partials 1929 1929 🚀 New features to boost your workflow:
|
mattcreaser
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A client created while the app was not in the foreground (for example from a background start or a service) started its launch session as active, so the session never paused or timed out, and the first foreground joined it. The client now checks whether the process has a visible activity when it is created and, if not, pauses the launch session so it times out like any other backgrounded session. A foreground service on its own does not count as foreground, which matches how the lifecycle observer tracks started activities.