-
-
Notifications
You must be signed in to change notification settings - Fork 465
fix(android): Improve app start type detection with main thread timing #4999
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
markushi
wants to merge
8
commits into
main
Choose a base branch
from
fix/app-start-warm-detection
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
e7047cb
fix(android): Improve app start type detection with main thread timing
markushi 4164619
Update CHANGELOG.md
markushi 70879c1
Reduce number of foreground checks and add maestro tests
markushi 1547b1f
Merge branch 'main' into fix/app-start-warm-detection
markushi acf7e58
Merge branch 'main' into fix/app-start-warm-detection
markushi b0722d3
Merge branch 'main' into fix/app-start-warm-detection
markushi 7034d95
Update Changelog
markushi ef2b3bf
Switch to MessageQueue.IdleHandler
markushi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incorrect boolean value in onActivityDestroyed sets wrong foreground state
Medium Severity
In
onActivityDestroyed(),appLaunchedInForeground.setValue(true)is set when the app moves to background, but the original code set it tofalse. The comment explicitly states "if the app is moving into background", yet the value is inverted. This causes warm starts to potentially be misclassified as cold starts when a user returns from background very quickly (within the same millisecond asfirstIdle), because the!appLaunchedInForeground.getValue()check that previously caught this case now fails, and thefirstIdletiming check uses strict>comparison which can miss edge cases.