-
Notifications
You must be signed in to change notification settings - Fork 1
Installation Guide From GitHub
Android and Google Play Protect actively try to stop users from installing apps that don't come from the Play Store. This is a security feature, not a bug — but it can confuse people trying to install Messages app from GitHub Releases or F-Droid. This guide explains why it happens and exactly how to solve it, on every Android version.
- Why Does This Happen?
- Solution 1: Allow Installs From Your Browser/File App
- Solution 2: Bypass a Google Play Protect Warning
- Solution 3: Disable Play Protect Scanning (Advanced)
- Solution 4: MIUI / Samsung / OEM-Specific Blocks
- Solution 5: "App not installed as package appears to be invalid"
Since Android 8.0 (Oreo), Google removed the old global "Unknown Sources" toggle and replaced it with per-app permission. Additionally, Google Play Protect (built into Play Services on almost all Android phones, even without the Play Store app open) scans any APK you try to install — including ones from GitHub or F-Droid — and may show a warning or block it outright if:
- The app isn't recognized by Google's servers (common for small/new open-source apps)
- The app requests sensitive permissions (like SMS, which Messages app needs)
- The APK is unsigned, differently signed, or not yet "reputation-verified"
None of this means app is unsafe — it just means Google hasn't scanned/whitelisted it the way it does Play Store apps. This is expected for open-source, offline apps that intentionally avoid Google services.
This is the most common block, and the standard fix.
- Try installing the APK — Android shows: "For your security, your phone is not allowed to install unknown apps from this source."
- Tap Settings on that prompt
- Toggle Allow from this source ON
- Return and tap Install again
Manual path:
Settings → Apps → Special app access → Install unknown apps → [choose Chrome/Files/Downloads] → Allow from this source
Note: This permission is granted per app, not system-wide. If you download the APK with Chrome, only Chrome gets permission — not your file manager.
If Play Protect flags the APK during or after install, you'll see one of these:
- "Blocked by Play Protect"
- "App isn't from Play Store, and may be harmful"
- "Play Protect doesn't recognize this app"
- When the warning appears, look for "Install anyway (unsafe)" or More details → Install anyway
- If installed already and Play Protect is repeatedly re-scanning/nagging:
- Open Play Store app → Profile icon → Play Protect → Settings (gear icon)
- Turn off "Improve harmful app detection" (optional — sends less data to Google, doesn't disable protection entirely)
⚠️ Only do this for apps you trust and have verified (see the checksum verification steps in the Installation Guide). Don't casually disable Play Protect for every unknown APK.
Only needed if Play Protect keeps auto-uninstalling or repeatedly blocking Messages app even after you've allowed it once.
- Open Google Play Store
- Tap your profile icon (top right)
- Tap Play Protect
- Tap the gear/settings icon
- Toggle OFF: Scan apps with Play Protect
⚠️ This disables malware scanning for all apps on your device, not just Messages app. Recommended only temporarily, or for advanced users who understand the tradeoff. Turn it back on afterward if you're cautious.
Some Android skins add extra layers on top of stock Android's blocks.
- MIUI often blocks installs silently with no clear error.
- Fix: Settings → Apps → Permissions → Install via USB / Unknown sources, and also disable "MIUI Optimization" under Developer Options if installs keep failing.
- You may also need: Security app → Settings → disable "Verify apps over USB" and turn off "Provide anonymous data usage" temporarily.
- Samsung sometimes shows "Blocked by Samsung Knox" for SMS-permission apps.
- Fix: Settings → Biometrics and security → Install unknown apps → enable for your browser/file manager.
- Should work normally since there's no Play Protect layer — just enable Unknown Sources as in Solution 1.
This isn't a Google Play Protect block — it's usually one of:
| Cause | Fix |
|---|---|
| Corrupted/partial download | Re-download the APK, verify the SHA-256 checksum |
Older Android version than minSdkVersion
|
Check your Android version meets Messages app's requirement |
| APK downloaded via a browser that "helpfully" renamed the extension | Rename file back to .apk and reinstall |
| Conflicting existing install with different signing key | Uninstall the old version first, then reinstall |
See also: Installation Guide for the full install walkthrough from F-Droid and GitHub Releases.