Require immediate Google Play updates - #541
Open
frankii91 wants to merge 1 commit into
Open
Conversation
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.
Summary
Motivation
Google Play background updates are optional and are not guaranteed to run promptly. Without an in-app update check, an authenticator can continue running an obsolete client even when a newer Play release contains important security, protocol-compatibility, or reliability fixes.
The application previously had no active update path. This change asks the Google Play runtime for the authoritative update state and blocks access only when Play reports both that an update is available and that the immediate flow is allowed.
Once the gate is shown, it cannot be dismissed by tapping outside it or using the system back action. If starting the Play flow fails or the user returns from it without updating, the gate remains visible and the update can be retried.
Unchanged behavior
Validation
netknightsdebug APK build: passedgit diff --check: passedThe current upstream analyzer baseline remains non-zero with 58 existing diagnostics (57 info diagnostics and one
invalid_annotation_targetwarning inlib/model/token_folder.dart). None are introduced by this change.