Add Play Protect troubleshooting to install instructions#9
Open
undisputedP wants to merge 1 commit into
Open
Conversation
Several users have hit Google Play Protect blocking the install. This isn't something we can fix from the app side — the combination of VpnService + AccessibilityService + an unknown signer is exactly the fingerprint Play Protect flags by default. Document the workarounds prominently so users find them before giving up: - "Install anyway" — covers ~80% of cases - Temporarily toggle off Play Protect — covers the rest - adb install — cleanest path for power users - Obtainium — best long-term answer for users who want auto-updates from GitHub releases without going through Play Protect each time - F-Droid — the structurally correct long-term answer (a trusted FOSS source bypasses Play Protect entirely); flagged as "submission in progress" since that's a real future task Also added a short "Why does Play Protect flag this?" subsection explaining the legitimate reasons we ask for the two permissions. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Documents the Play Protect workarounds so users hit by the warning don't give up. No code change — README only.
Covers, in priority order:
Plus a short "why does this happen" explanation: VpnService + AccessibilityService + unknown signer is exactly Play Protect's heuristic, and the permissions are doing what's described in How it works.