This message means exactly one thing: the system opened the file, tried to read its manifest — and failed. The word “parsing” has nothing to do with it; the error is not in the text, but in the package itself or in the fact that it is not a package at all. There are exactly five causes, and they are ordered by decreasing frequency. Check them in order — usually everything ends at the second one.
1. The file was not downloaded completely
Cause. Connection dropped midway, storage filled up, the browser was closed before the download finished. Android receives a truncated zip, cannot find the end of the archive in it, and gives up.
How to check. Compare the size of the downloaded file with what is listed on the app page — it is shown there before download. The median size of the files we distribute is 61.8 MB, but 297 files out of 1031 are heavier than 100 MB, and the heaviest is 391 MB. On mobile internet, this breaks regularly.
What to do. Delete the file and download it again, preferably over Wi-Fi and not through a third-party download manager. Our file link is temporary and lives for 15 minutes: if the download took longer, resuming will hit an expired link and write an error page into the file instead of data. Start the download again from the app page.
2. This is not an APK, but a container
Cause. Files .xapk, .apkm,
.apks are archives with a set of app parts (base + resources for
your screen and language). Tapping such a file will not install anything: Android installs
sets only via an install session, which is opened by Google Play or
an app with permission to install packages.
How to check. Look at the extension in a file manager, not the icon. Some managers show the “green robot” for anything that looks like an archive.
What to do. We have 1024 pages out of 1031 that deliver a regular
single .apk — it installs with a tap. Five pages deliver
.xapk: they require an installer that can unpack the container and
install the parts in one session. Renaming .xapk to
.apk is useless — changing the extension doesn't change the contents, and
the error will remain the same.
3. Installation from this source is not allowed
Cause. On Android 8.0 and later, the permission is granted not to the system as a whole, but to a specific app — the one from which you open the file. You allowed the browser, but tapped the file in the file manager — the file manager does not have the right.
How to check. Settings → Apps → the app you need → “Install unknown apps”. On Android 7.0 and lower, this is one common toggle in the “Security” section.
What to do. Grant permission to exactly the app from which you launch the installation, and repeat. After installation, the permission can be revoked — it is not needed permanently.
4. The app requires a newer Android than yours
Cause. The package manifest records the minimum API level. If it is higher than the phone's, some firmware builds honestly say “App not installed”, and some say exactly “There was a problem parsing the package”.
How to check. System version: Settings → About phone → Android version. The app's requirement is written on the app page, in the specifications row.
What to do. Take what will actually install. Based on a measurement of our catalog on 09.09.2026: on Android 5.0 and lower, 38 apps can be installed, on Android 6.0 and lower — 183, on Android 7.0 and lower — 533. The remaining 462 pages require Android 8.0 and higher, and nothing will save them on an old device. The second path is an older version of the same app: 365 pages in the catalog have more than one build, and for 31 of them the old version requires Android lower than the current one. The version list opens from the app page — for example, for WhatsApp Business the current build asks for Android 6.0, while the previous one gets by with Android 5.0.
5. The file is corrupted after downloading
Cause. An archiver “optimized” the APK, an antivirus cut out a piece, the file was run through a cloud service that recompressed the contents. Any change inside the package after signing breaks both the signature and the structure.
How to check. We print the SHA-256 of each file on the app page before download. Calculate the hash of the downloaded file (many file managers and any desktop can do this) and compare character by character.
What to do. If it doesn't match, download again and don't run the file through archivers and “cleaners”. If it matches and the error remains, the cause is not in the file: go back to points 3 and 4.
What you shouldn't do
- Install “parsing error fixers” from app stores. They cannot read the manifest for the system: the installation is performed by Android itself, and no third-party app is embedded in this process.
- Change the file extension. Neither
.zip→.apk, nor the reverse, fixes anything. - Disable Play Protect “just in case”. It gives a different message — about a blocked app, not about package parsing.
If the message was different
We discuss similar but different errors separately: “App not installed” — there, in most cases, the culprit is a signature conflict with the version from Google Play; “Package is invalid” — this is about the signature and integrity; “Not supported on the device” — about the Android version and processor architecture. A general checklist for all cases is in the article “APK won't install”.
