Google increments minimum target API for apps in 15
In Android 15, Google is incrementing the security policy blocking the installation of old applications to include Android 6.0
What’s changing
From Android 15 it is no longer possible to install any application that targets an API level below 24 - Android 7.0. Attempting to do so will trigger a security exception.
Will this have any impact on EMM-deployed devices?
Yes. If a device is enrolled with, or upgraded to Android 15, it will no longer be possible to install old Android applications. Devices with apps already installed will not be affected.
Do my enterprise apps have to target API level 35 (Android 15)?
No. It's certainly better to ensure apps are targeting the latest API level where possible, but as long as applications target an API level of 24.(Android 7.0) or higher for Android 15, apps will continue to be able to install without issue
Is it possible to test the changes?
Yes, on an Android 15 device you may connect to ADB and sideload an application with:
adb install name_of_package.apk
This will result in an error similar to:
INSTALL_FAILED_DEPRECATED_SDK_VERSION: App package must target at least SDK version 24, but found 22
To overcome this error and install the application anyway, use:
adb install --bypass-low-target-sdk-block name_of_package.apk
Note this only works via ADB, there are no other means of bypassing the SDK block.
For more information, read on.
Feel free to forward this message on to your colleagues/peers, and connect with me on LinkedIn.
🛟 For help or guidance, feel free to reach out.
👋, Jason