Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

An app will not install on Android 14 because its target SDK is too old

ErrorINSTALL_FAILED_DEPRECATED_SDK_VERSION: App package must target at least SDK version 23, but found 7

Short answer

Android 14 refuses to install any app whose targetSdkVersion is lower than 23. Logcat shows INSTALL_FAILED_DEPRECATED_SDK_VERSION. For your own app, raise the target SDK, rebuild and test. For an old APK you only want to try, adb install has a bypass flag meant for testing. Apps already installed before the update stay.

  • Applies to Android 14 (API 34) and later, Android Gradle Plugin 8, adb 35
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Install the file with adb and read the exact failure. The number after 'but found' is the targetSdkVersion in that APK.

    adb install app-debug.apk
  2. 2Match what you see, then jump to its fix

    1. 1The failure says 'but found' followed by a number lower than 23, on an Android 14 or newer deviceYour app declares a target SDK below 23Fix
    2. 2The APK comes from an archive or a third party, and you have no source to changeYou are installing an old APK you cannot rebuild, only to test itFix

What does the error look like?

  • INSTALL_FAILED_DEPRECATED_SDK_VERSION: App package must target at least SDK version 23, but found 7
  • INSTALL_FAILED_DEPRECATED_SDK_VERSION

Cause 1 of 2

Your app declares a target SDK below 23

1Check

The rule applies to every app on Android 14, whatever you compile against. Look for the value in the manifest and in the module's Gradle file; Gradle values are merged into the final manifest.

grep -rn "targetSdk" --include=AndroidManifest.xml --include=build.gradle --include=build.gradle.kts .

2Fix

Raise the target to a current API level and test the app on that level, because a higher target switches on the newer platform behaviours. The attribute is android:targetSdkVersion in the uses-sdk element, or targetSdk in defaultConfig.

// app/build.gradle.kts
android {
    defaultConfig {
        targetSdk = 35
    }
}

3Verify

Rebuild and install on the Android 14 device.

./gradlew assembleDebug
adb install -r app/build/outputs/apk/debug/app-debug.apk

Confirmed by developer.android.com

Did this fix it?

Cause 2 of 2

You are installing an old APK you cannot rebuild, only to test it

1Check

The platform provides one escape for testing. It is not a way to ship, because the block is on by default on user devices.

adb devices

2Fix

Add the bypass flag to the adb install command. Use it for testing only.

adb install --bypass-low-target-sdk-block old-app.apk

3Verify

adb prints Success, and the app appears on the device.

adb shell pm list packages | grep -i example

Confirmed by developer.android.com

Did this fix it?

How do I stop it coming back?

  • Keep targetSdk current at every release, and read the behavior-change page for each new Android version first.
  • Do not keep an old prebuilt APK as a deliverable; rebuild it from source.
  • Test on a device or emulator that runs the newest Android version, not only the oldest you support.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Play Console will not accept the release because of its target API level

A target API level warning on the Policy status page, with an extension form link

Since 31 August 2026, Google Play accepts new phone and tablet apps and updates only if they target Android 16 (API level 36); the extension window ran to 1 November 2026.

5 causes, each with a fix

Mobile apps

Android Studio cannot pair the phone over Wi-Fi

The Pair devices over Wi-Fi dialog lists no device

Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.