Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

v4.2.7 APK hard-blocked by Google Play Protect (no install bypass) — stricter than #357

Open
  • Is something wrong?
#583 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile-dev, release, security

Research direction

Start by reviewing the v4.2.7 standard APK and the related #357 discussion, then confirm whether the Play Protect hard block is reproducible and tied to the release signing or CI setup. Done means the block is resolved or users have clear, safe installation guidance, including any available trusted distribution option.

Written by the indexing model from the issue text.

Description

Summary

Installing the LeanType 4.2.7 APK from the GitHub release page is hard-blocked by Google Play Protect on the latest Android. The install is refused outright (not just a dismissible side-load warning).

What happens

Attempting to install 1-LeanType_4.2.7-standard-release.apk from the v4.2.7 release triggers a Play Protect hard block:

  • Title: "App blocked to protect your device"
  • Body: "This app can request access to sensitive data. This can increase the risk of identity theft or financial fraud."
  • Only an OK button is offered — there is no "Install anyway" option, so the APK cannot be installed at all.

This is stricter than the usual "unrecognised app" download warning: it is a full block with no bypass.

Environment

  • Device: Android (latest), Google Play Protect active
  • Release: LeanType v4.2.7 (standard flavor, ~11.1 MB)
  • Source: GitHub Releases (https://github.com/LeanBitLab/LeanType/releases/tag/v4.2.7)

Expected behaviour

LeanType is a popular, legitimate open-source keyboard. Users should at least be able to install it, ideally via an installer that Play Protect trusts (see #357), or be given guidance on a safe install path.

Notes / relation to earlier report

Related to closed #357 (July 2026, same Play Protect issue). One maintainer comment there suggests using Obtainium (ImranR98/Obtainium), which is a good mitigation for advanced users, but it does not help less-technical users, and this v4.2.7 report shows Play Protect escalating to a hard block rather than only a warning.

Suggested action

  • Confirm whether this is a false positive tied to the current signing/CI setup.
  • If a Google Play listing is planned/available, point users there.
  • Otherwise, document the recommended safe install path (e.g. Obtainium, or disabling Play Protect for this known app) in the release notes, since the block message will discourage many users.

Thanks for the great project — flagging so others don't get stuck.

Dominant language
Kotlin
Stars
1k
Forks
59
Avg merge
13h 11m
Merged PRs (30d)
47

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LeanBitLab/LeanType

All issues in LeanBitLab/LeanType

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.