fix: Improve application opened event reliability #165
+59
−36
Conversation
This file contains 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
yuhao900914
reviewed
May 14, 2024
github-actions bot
pushed a commit
that referenced
this pull request
May 15, 2024
## [1.5.1](v1.5.0...v1.5.1) (2024-05-15) ### Bug Fixes * Improve application opened event reliability ([#165](#165)) ([d3b9de7](d3b9de7))
|
🎉 This PR is included in version 1.5.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Summary
Background tasks can launch an app without it ever being foregrounded, meaning our application opened event is not accurately being recorded. This mirrors changes in Amplitude-iOS that use application state to detect whether an app launch was from the background vs tracking didEnterForeground and didFinishLaunching notifications to infer background state.
Checklist