“This app was developed for use on an older version of Android and may not work properly” is the message many users see when installing apps outside of Google Play, starting with Android 12, a Google Play Protect warning that points to the lack of newer privacy protections, and is often unbearable.
When we install an older APK on a modern phone, the system checks its target API level and, if it’s more than two versions lower than the installed Android version, it warns us that it lacks the latest security and privacy improvements. This measure is intended to protect us from really old apps, although it can sometimes be annoying for those working with legacy software, or in other words, old apps.
Why does the message appear?
Since version 12, Android includes a Play Protect warning mechanism that detects when an app declares a targetSdkVersion that’s much lower than the device’s API level. If, for example, your phone is running Android 13 (API 33) and you try to install an app designed for API 29 or lower, you’ll see a warning indicating that the app doesn’t incorporate recent protections. What you really need to know is that the app in question is old, and if the message appears, that’s why.
Of course, this means you’ll have to click ” Install Anyway ” to continue, although some manufacturer layers (Samsung, Xiaomi) may block the installation altogether. Developers receive reports of failed installations and negative reviews from users who don’t understand the real reason; additionally, Google Play now requires a minimum targetSdkVersion for new apps and recent updates.
More specifically, having a low targetSdkVersion means it has a flag indicating which Android version the app is optimized for. If it’s too outdated, the system won’t consider it compatible with the new permission restrictions, and this is done to avoid problems with viruses or various types of phishing.
Starting in November 2022, all new or updated apps on Google Play must target at least API 31 (Android 12), so these restrictions will be enabled.
On the other hand, we also have framework compatibility, which means that changes in storage management, location permissions, and other behaviors can cause older apps to malfunction or expose sensitive data, so everything related to this is also restricted, and you also ensure that your data is not manipulated by third parties.
How to fix it
In the hypothetical case of being a developer, or wanting to inform someone because you love your favorite app, what you need to do is update the targetSdkVersion in the build. Gradle to the level required by Google Play and test the app on Android 12 and 13 to correct possible incompatibilities with the system.
For advanced users, you can also try installing manually via ADB with the –bypass-low-target-sdk-block option and, after the warning, confirm “ Install anyway .” This will cause the app to install and stop bothering you once and for all. However, if the app has vulnerabilities, it will be up to you.
