android: Log resolved installer package at app update check start#210
Merged
Conversation
Resolve the installer package (getInstallSourceInfo on API 30+, the deprecated getInstallerPackageName below it; null on failure) and log it as debug at the start of the update check flow, instead of blocking the Play update check for non-Play installs. Adds the PLAY_STORE_PACKAGE constant in prep for gating the Play flow on it later, and uses it in getPlayStoreMarketIntent in place of the hardcoded string.
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
2 participants
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.
Splitting from #206, see description and discussion there.
Idea is to eventually block update checks if not installed through gplay, this is the preparation for it to safely confirm that we're resolving correctly.