Fix "App not installed" and other install errors
When an APK won't install, Android's message is short and doesn't always say why. These are the five causes that can apply to the apps on Gamekosh, the message you are likely to see, and what to do about it.
Your browser isn't allowed to install apps
What you see: a message that, for your security, your phone isn't allowed to install unknown apps from this source.
Why: Android 8.0 and newer only install APKs opened from an app you have allowed, and your browser or Files app hasn't been allowed yet. It happens once, with whichever app you install first.
Fix: tap Settings in the message, switch on Allow from this source, go back and tap Install.
The download is incomplete
What you see: There was a problem parsing the package, or on newer phones, App not installed with a note that the package appears to be invalid.
Why: the download stopped partway, so Android can't read the file.
Fix: delete the file, download it again and compare its size in bytes with File check on the app's page. A complete Goplay11 file is 3,340,748 bytes, for example; anything smaller is cut off.
Your Android version is too old
What you see: usually the same parsing message, or just App not installed.
Why: every app here except LuckX needs Android 7.0 or newer. On a phone with Android 6.0, LuckX is the only one that installs.
Fix: nothing on the phone will change it. Six of the apps also open in a browser, as app or browser explains.
The app has no code for your phone's processor
What you see: App not installed. Some Android versions add that the app isn't compatible with your phone.
Why: MMY ships native code for 64-bit ARM phones only (arm64-v8a), so a phone running 32-bit Android can't install it, whatever its version. The other apps carry code for all four processor types or, like LuckX, none at all.
Fix: there is none for MMY on a 32-bit phone. Older and 32-bit phones lists the apps that do install.
A newer or differently signed copy is installed
What you see: App not installed. Depending on the Android version, the message adds that the package conflicts with an existing package.
Why: Android only replaces an installed app with a file that has the same package id, the same certificate and a version code at least as high. Two older builds of these apps fail that test: Come 1.10, which Come's download page names in its default settings, and the earlier Hero11 build 1.13.f675. Both are older than what the buttons give, so Android refuses them as downgrades.
Fix: keep the app you have. If you really want the other file, uninstall the app first, which deletes everything it stored on the phone, your sign-in included.
Two more things to check
- Storage. If Android says there isn't enough space, free some up. MMY's download alone is 20.95 MB, every other app's is 6.89 MB or less, and the installed app needs more than its download.
- Play Protect. If Google Play Protect blocks an app as harmful, don't install it. A warning that it doesn't recognise the developer is different: Google doesn't know who made the app, which is common for apps that aren't on Google Play.
Related guides
- Install an APK on AndroidAllow the installer once, read the prompt, and what differs between Android versions.
- Older & 32-bit phones: which apps installThe Android version and processor types each APK needs.
- Update an APK app without losing your dataWhen a newer file installs over the old one, and when Android refuses it.