By Macro Panel Info Editorial · Published 2026-11-07 · Updated 2026-11-07 · 9 min read

You've downloaded the file, allowed your browser to install it, tapped Install, and Android says "App not installed". No explanation, no error code, just a flat refusal and a button labelled OK. It's one of the most irritating messages on the platform, mostly because the same words cover half a dozen unrelated problems.

The good news is that the causes are limited, and you can usually work through them in a sensible order and find the culprit in a few minutes. This guide covers the common install errors, what each one usually means, and nine fixes ranked from "try this first" to "last resort". Where it matters, we'll refer to the Macro Space APK, since a lot of readers are trying to install that one.

Start by reading the message properly

Android's wording is vague, but the exact phrase narrows things down. Here's a quick map before we get into the fixes.

"App not installed"	The catch-all. Often a signature conflict with an existing copy, a damaged file or too little storage.
"App not installed as package appears to be invalid"	The file is probably corrupt or incomplete, or it isn't a real APK.
"There was a problem parsing the package"	Android couldn't read the file. Causes include a broken download, a wrong file type or an app built for a newer Android version than yours.
"Blocked by Play Protect"	Google's scanner didn't like the file, or hasn't seen it before. Read the dialog for detail.
"For your security, your phone is not allowed to install unknown apps from this source"	The permission isn't switched on. See our guide to that setting.
"Installation blocked" or "blocked by administrator"	A work profile, parental control or a manufacturer feature is stopping it.
"App not compatible with your device"	The app needs a newer Android version, or a feature your phone lacks.

Fix 1: Check you really downloaded an APK

It sounds obvious, but a surprising number of failed installs come down to the wrong file type. Open your Downloads folder and look at the full name. It should end in .apk. If it ends in .zip, .xapk, .apks or .apkm, it's a bundle that a normal tap can't install. If it ends in .exe or .html, you've downloaded something else entirely, possibly a fake. And check the size: the Macro Space file we examined is about 8.7 MB. A file of a few kilobytes is almost certainly a web page saved with the wrong name.

Fix 2: Re-download the file

A broken download is the single most common cause of "package appears to be invalid" and parse errors. Mobile connections drop, browsers pause and resume, and storage can run out mid-download. Delete the file and download it again over a steady Wi-Fi connection. Download it directly in your browser, not through an accelerator or a third-party manager, which can alter files. When it finishes, check the size against what the source says, and for extra certainty compare the fingerprint using our checksum guide.

Fix 3: Uninstall any older copy first

This one catches many people. Android only lets an app update itself if the new file is signed with the same key as the one already on the phone. If you previously installed the app from another source, or an earlier file used a different key, Android blocks the update to protect you from impostors. The result is "App not installed" with no further detail. To fix it, uninstall the old copy completely. Open Settings, Apps, find the app, and tap Uninstall. Be aware that you lose any data stored in the app, so back up anything important first. Then install the new file fresh.

Fix 4: Free up storage

The installer needs room to unpack the app, usually two to three times the size of the APK, plus a margin. If your phone is nearly full, installs can fail silently. Aim for at least a few hundred megabytes free. Clear cached files, delete old downloads and move photos to a cloud service or a computer. Then try again.

Fix 5: Restart the phone

It's the classic advice, and it's classic because it works. A phone that's been running for weeks can have a stuck package installer, a full temporary folder or a background service in a bad state. Restarting clears all of that. Switch it off, wait ten seconds, switch it on and try the install again.

Fix 6: Read the Play Protect message

If Play Protect interrupted the install, don't just dismiss it. Tap "More details" and read what it says. A generic message about an unknown developer is common for small apps and doesn't mean the file is bad. A specific warning that names a threat should be taken seriously, and in that case you should stop. If you do decide to continue, choose "Install anyway" for this one file, and don't switch Play Protect off altogether to push past an error. For how to judge whether to go ahead, the safety checklist is the place to start.

Fix 7: Check your Android version

Every app declares the oldest Android version it supports, and a newer app can refuse to install on an older phone. In the other direction, new Android releases are stricter about old apps. From Android 14, the system blocks installing apps that were built for very old Android versions, a measure to reduce malware that exploits legacy behaviour. If a very old APK fails on a new phone with a vague error, this might be why. The developer lists Android 4.1 and up for the Macro Space file, so a modern phone is unlikely to hit a minimum-version problem with it.

To check your own version, open Settings, About phone, and look for Android version.

Fix 8: Look for blocks from admins, profiles and manufacturers

Some phones have extra layers that sit on top of the standard permission:

Work or school profiles can forbid installs from outside the store. If the option is greyed out, that's likely why.
Parental controls, such as Family Link, can block installs.
Samsung Auto Blocker on recent devices can stop installs from unofficial sources until you turn it off for the moment.
Xiaomi, Oppo and Realme phones sometimes add a "security check" or "install via USB" toggle in Developer options that blocks sideloading. On Xiaomi, turning off MIUI optimisation in Developer options has resolved some installs, though newer HyperOS versions may differ.
Secure folders and multiple users keep permissions separate. Make sure you set the permission in the same space where you're installing.

Fix 9: Install through a different route

If everything else has failed, try changing how you launch the install. Instead of tapping the file in the browser's download list, open a file manager, navigate to the Downloads folder and tap the APK there. Don't open it from inside a zip file or from a messaging app's cache, as both can cause parsing problems. If you have a computer, you can install over USB using Android's debug bridge. Enable Developer options and USB debugging, connect the phone, and run:

adb install -r Macro-Space.apk

Unlike the on-screen installer, ADB prints a specific failure code, which makes diagnosis much easier.

Decoding ADB error codes

INSTALL_FAILED_UPDATE_INCOMPATIBLE	A copy with a different signature is already installed. Uninstall it first.
INSTALL_FAILED_INSUFFICIENT_STORAGE	Not enough free space.
INSTALL_FAILED_OLDER_SDK	The app needs a newer Android version than the phone runs.
INSTALL_PARSE_FAILED_NOT_APK	The file isn't a valid APK.
INSTALL_PARSE_FAILED_NO_CERTIFICATES	The file isn't signed, or its signature is broken.
INSTALL_FAILED_USER_RESTRICTED	A manufacturer or admin setting is blocking the install.
INSTALL_FAILED_VERIFICATION_FAILURE	A verifier, usually Play Protect, rejected it.
INSTALL_FAILED_TEST_ONLY	The app is flagged as a test build and needs a special flag to install.

Testing whether the file itself is broken

An APK is really a ZIP archive with a special structure, which means you can test it on a computer before you waste more time on the phone. On Windows, install a free archive tool such as 7-Zip, right-click the APK, and choose the option to test the archive. If it reports errors, the file is damaged and no amount of fiddling with the phone will help. On macOS or Linux, unzip -t Macro-Space.apk does the same check from the terminal and ends with a line saying no errors were detected when the archive is sound.

A sound archive isn't proof the app is good, only that it isn't corrupted. Combine it with the fingerprint check from our checksum guide and you can be confident you have a complete, unaltered copy of what the source published.

A decision path in words

If you like to work methodically, this order saves the most time. First, confirm the file is an APK of the expected size. If it isn't, re-download. Second, if the message mentions permission or "unknown apps", fix the setting. Third, if the message is a plain "App not installed", uninstall any old copy and free some storage. Fourth, if it mentions parsing, check your Android version and test the archive. Fifth, if Play Protect is involved, read its message. Sixth, if you suspect a manufacturer or admin block, look at Auto Blocker, profiles and parental controls. Seventh, if all else fails, try ADB to get a specific code. Following that sequence stops you from jumping between random fixes.

Tablets, spare phones and other devices

The same rules apply on tablets and most other Android devices, with a couple of twists. Some tablets and TV boxes lack a standard file manager or restrict the unknown apps setting in odd places. Cheap devices sometimes have heavily modified Android versions that behave differently, and a few come with outdated security patches that cause installs to fail. If you're trying to install on an older spare device, remember that very old Android versions lack modern protections, so be doubly careful about what you put on them.

Problems after the install works

The app installs but won't open. Clear its storage and cache from the app info page, then try again. If it still closes immediately, the app may not be compatible with your phone, or the file might be broken in some way you can't see. A fresh download is worth a try.

The icon doesn't appear. Some launchers take a moment. Search for the app by name in the app drawer, or open it from Settings, Apps.

It asks for permissions you didn't expect. Stop and read them. If you aren't comfortable, uninstall. Our permissions guide explains what each one allows.

It worked before and doesn't now. An Android update may have tightened a restriction, or the app might depend on something that changed. Check the source for a newer version, and compare fingerprints before replacing it.

Habits that prevent most install problems

Download from a single trusted source over a stable connection.
Check the extension and size before you tap.
Keep at least a few hundred megabytes of free storage.
Uninstall old copies before installing a new build of the same app.
Keep Play Protect on and read what it says.
Switch the install permission off again afterwards.

A few special cases worth knowing

The error only happens with this one file. If other APKs install without trouble, the problem lies in the file or in its relationship to your phone, such as a signature clash with an old copy. That points you back to fixes two and three rather than to your device settings.

It installs on one phone and not another. Differences in Android version, manufacturer restrictions and storage are the usual causes. Compare the two devices' Android versions first, then check for Auto Blocker, profiles or admin controls on the one that fails.

The installer just closes. Some file managers crash while reading a bad package. Try a different file manager, or open the file from the system's Downloads app.

A friend sent you the APK. Files passed through messaging apps are sometimes recompressed or renamed. Ask for the original source or compare the fingerprint with the published value before you try to install it.

When to stop

It's tempting to keep trying more and more elaborate workarounds, but there's a point where the better answer is to walk away. If you've tried a fresh download, checked the fingerprint, uninstalled old versions and freed storage, and the install still fails, the file might simply be incompatible with your phone. If a page tells you to disable your antivirus, root your device or install a "patcher" to make the app work, treat that as a sign that something's wrong with the file, not with you.

If you'd like to go back to basics, the full install guide covers the clean path from start to finish, and our overview explains what the app is before you spend any more time on it. If you'd rather skip risk and still improve your game, here are the safer routes.

APK "App not installed" and "parse error": 9 fixes that work