“App Not Installed” or “Problem Parsing the Package” When Installing Mihon/Tachiyomi

ByAdmin

Short answer: “app not installed” usually means a signature conflict (another build with the same package name is already installed) or an incomplete download; “there was a problem parsing the package” usually means the file is corrupted, made for a different CPU architecture, or your Android is older than the app requires (Mihon needs Android 8.0+; Tachiyomi 0.15.3 needs 6.0+).

Signature conflict — the classic Tachiyomi/Mihon clash

Android refuses to install an app over an existing one if the signatures differ. Tachiyomi’s package is eu.kanade.tachiyomi; Mihon’s is app.mihon, and its FOSS build is app.mihon.foss — those three coexist fine. Conflicts appear when a fork or a modified build shares a package name with different signing: for example a modded “Tachiyomi” from a random site, then the genuine build on top. Fix: back up inside the installed app first (backup guide), uninstall the conflicting copy, then install the genuine APK and restore.

Corrupted or wrong file — verify before retrying

  1. Re-download the file; a cut-off download is the simplest cause of parse errors.
  2. Verify the SHA-256. Our Mihon page lists the official v0.21.2 hashes for every build, and the Tachiyomi page lists the archive-published hash for the universal package. A mismatch means do not install that file.
  3. Pick the right architecture: if you grabbed an x86 build for an ARM phone (or vice versa), use the universal APK instead — it contains all architectures.

Android version too old

Parse errors on old devices are often just the version floor: Mihon 0.21.x requires Android 8.0 (API 26). On Android 6/7 the install cannot proceed — Tachiyomi 0.15.3 (Android 6.0+) still installs there, which is one reason legacy users keep it. There is no workaround that makes a modern Mihon run on Android 6/7.

Other quick checks

  • Free up storage: installs fail silently when the device is nearly full.
  • If Play Protect blocks the install with a warning, do not just override it — verify the hash first (above). A matching hash from the official GitHub release is the real all-clear.
  • Installing via Shizuku or ADB shows the true error code; the installer option in Mihon is covered in our Shizuku guide.

Related: all troubleshooting guides

Similar Posts