Flutter: Android 14 API Level 34 Target Issue Continues Despite Updates

Why Am I Still Seeing an API Level 34 Warning?

In Flutter development, targeting the most recent Android API level is critical for assuring app compatibility with new features and security upgrades. Recently, after changing the targetSdkVersion to API level 34 (Android 14), developers reported that the Play Console still cautions that the app must target Android 14 or higher, despite a successful build.

This disparity might cause confusion, especially when previous app bundles are still running on the console. Understanding how prior versions affect the current upload and addressing this warning are critical for effectively releasing your Flutter app.

Understanding the Solution to API Level Targeting in Flutter

The first script modifies the Flutter project's Android setup to ensure that the app is properly targeting API level 34. The crucial commands are compileSdkVersion and targetSdkVersion, which specify the Android SDK versions used during compilation and deployment. Setting compileSdkVersion to 34 ensures that the program is built using Android 14, whereas targetSdkVersion specifies the intended Android version for the app to run on. These modifications update the project settings to meet the most recent Google Play Store submission standards, removing the warning regarding unsupported API levels.

The second script communicates with the Google Play Console API via Python. It automates the process of detecting and removing older software bundles that may cause issues. google.auth.default() returns the default credentials for accessing the Play Store API, whereas build('androidpublisher', 'v3') initializes the Google Play Developer API. The script then utilizes service.edits().bundles().list() to get active app bundles, and if an old version is discovered, service.edits().bundles().delete() deletes it. Finally, the service.edits().commit() command saves and applies all changes, guaranteeing that the app is clear of any outdated bundles that could cause the error message.

android {
    compileSdkVersion 34
    defaultConfig {
        applicationId "com.example.myapp"
        minSdkVersion 21
        targetSdkVersion 34
        versionCode 1
        versionName "1.0"
    }
}

import google.auth
from googleapiclient.discovery import build
credentials, project = google.auth.default()
service = build('androidpublisher', 'v3', credentials=credentials)
package_name = 'com.example.myapp'
edit_id = service.edits().insert(body={}, packageName=package_name).execute()['id']
bundles = service.edits().bundles().list(packageName=package_name, editId=edit_id).execute()
for bundle in bundles['bundles']:
    if bundle['versionCode'] == 1:  # First build still active
        service.edits().bundles().delete(packageName=package_name, editId=edit_id,
                                        bundleId=bundle['id']).execute()
service.edits().commit(packageName=package_name, editId=edit_id).execute()

Resolving Conflicting Bundles in Flutter App Updates.

One common issue when updating a Flutter app's targetSdkVersion is the presence of old app bundles that are still shown as active in the Google Play Console. Even if these bundles are out of date, they can prevent the most recent build from being properly recognized, resulting in warnings like "App must target Android 14 (API level 34) or higher." While changing the targetSdkVersion to 34 is required, developers must also ensure that previous versions do not disrupt the update process. Managing app versions, particularly eliminating obsolete bundles, can help to resolve this issue.

In addition to appropriately defining the target API level in the build.gradle file, active versions should be reviewed on a regular basis in the Google Play Console. Developers should use tools like the Google Play Developer API or manually disable outdated packages. This ensures that the Play Store accurately reflects the most recent build configuration. Because Google Play requires apps to follow rigorous versioning criteria for updates, controlling both the code and bundles within the Play Console guarantees a smooth transition and reduces the likelihood of encountering unresolved API level warnings.