Fix App Not Installed on Android 15: Safe Checks & Developer Notes

If Google Play Protect warns about an app, stop and verify it with the publisher rather than turning protection off. Play Protect scans apps from Google Play and other sources, and Google recommends keeping it enabled.

2. Check that the app supports your device

Confirm the app’s stated Android version and device requirements. Some apps include native libraries for particular processor architectures; an APK intended for a different device variant may not work. If the publisher provides a device-specific build, use its official instructions rather than changing the APK yourself.

Some apps are delivered as a set of split APKs or through a store-specific installer. If you have only one file from a bundle, use the publisher’s recommended installer or download the app through its official store instead of trying to install a partial package.

3. Check for an existing installation and protect its data

An update normally needs to be signed with the same app-signing certificate as the installed version. A build signed by a different certificate may not update it. Before removing an existing app, back up anything important: uninstalling may delete data stored only on the device. If this is an official app, ask its publisher how to move to the correct signed release.

4. Check storage and restart

Open Settings → Storage (the exact menu name can vary by device) and make sure the phone has room for the download and installation. Free space only by removing files you no longer need, then restart the phone and try the trusted, compatible installer again.

5. Understand Android 15’s older-app restriction

Android 15 blocks new installations of apps whose targetSdkVersion is below 24. Google explains that this change helps prevent apps from avoiding newer security and privacy protections. Apps below that target that were already installed before a device upgrade can remain installed, but this does not make them installable as new apps on Android 15. If an old app is blocked, look for a maintained version from its developer; do not use ADB or another tool to bypass the block.

6. If installing inside Private Space

Private Space must be unlocked before installing an app there. Unlock it on the device and use the on-screen installer; do not use ADB user IDs or other workarounds.

7. If it still fails

Write down the exact error, app name and version, Android version, device model, and where the installer came from. Share those details with the app’s publisher or device manufacturer. If the warning comes from Play Protect, do not ignore it simply to complete the installation.

Developer note: when 16 KB page sizes matter

This section is for app developers and build maintainers, not end users. A 16 KB page-size issue is not a general fix for every “App not installed” message. It matters for apps that include native .so libraries on devices using 16 KB pages. Two different things must be correct: the ELF load-segment alignment inside each native library, and the ZIP alignment of uncompressed native libraries inside the APK. ZIP alignment alone cannot repair a library built with incompatible ELF alignment.

For builds with uncompressed native libraries, use Android Gradle Plugin (AGP) 8.5.1 or newer so packaging can align them for 16 KB devices. For native code, NDK r28 and newer produces 16 KB-aligned ELF segments by default. With NDK r27 or older, Android documents these linker flags:

-Wl,-z,max-page-size=16384
-Wl,-z,common-page-size=16384

Also check all native dependencies and test the app on a 16 KB environment. Updating zipalign settings cannot substitute for rebuilding incompatible .so files.

Android Studio/AGP generally handles APK alignment automatically. If maintaining a custom build pipeline, the documented commands are:

zipalign -P 16 -f -v 4 input.apk aligned.apk
zipalign -c -P 16 -v 4 aligned.apk

Here, -P 16 requests 16 KiB alignment for uncompressed native libraries; 4 is the required alignment for other APK entries. The second command checks alignment. Run alignment before signing; do not modify an already signed APK and then distribute it. Do not use the deprecated -p option with a size argument.

Do not recommend patchelf as an end-user repair, or tell readers to re-sign a third-party APK with a debug key. Debug certificates are insecure by design, and changing an app’s signing identity can prevent it from updating as the same app. Rebuild and sign the developer’s own app through its normal release process.