Resolving Google Play's "Target Android 13 (API 33)" Warning

Problem Statement

You've configured your app with targetSdkVersion 33 in your build.gradle, yet Google Play Console still displays this warning:

Warning: App must target Android 13 (API level 33) or higher. It does not

The warning persists because Google Play requires all active app bundles across all tracks (including testing and paused releases) to meet the target API requirement. Even if your current production version targets API 33, outdated bundles in your testing tracks or older releases can trigger this alert.

Recommended Solutions

Key Insight

You must update every active track in Google Play Console with an API 33-compliant app bundle - even inactive/paused tracks with active bundles need attention.

Step 1: Locate Non-Compliant Bundles

Navigate to:

1. Play Console Inbox
2. Open the target API warning message
3. Click View details → View app bundles

Alternatively use App Bundle Explorer:

• Filter by Release status = Active
• Identify bundles targeting SDK < 33

Step 2: Update Each Affected Track

For every track with non-compliant bundles (Internal Testing, Closed Testing, Production, etc.):

1. Go to the track's management page
2. Click Create new release
3. Select your API 33-compliant app bundle
4. Complete review submission and PUBLISH

Critical

Even if a track is "paused," you must update its bundle and publish the change

Step 3: Verify Resolution

1. Return to the warning in your Inbox
2. The View affected app bundles button should disappear
3. You'll receive confirmation:

A recent policy warning about your app has been addressed

Handling Time-Sensitive Cases

If approaching Google's deadline (original was Aug 31, 2023):

1. Open the warning in your Inbox
2. Click View details
3. Request additional time via the official form

Alternative Fix Path

Promote compliant bundles through testing tracks sequentially:

1. Update Internal Testing → Publish
2. Promote same bundle to Closed Testing → Publish
3. Promote same bundle to Open Testing → Publish

Why This Happens

Google Play enforces API requirements globally across all release channels. Common triggers:

• Old bundles lingering in testing tracks
• "Paused" releases still considered active
• Compliance checks scanning all tracks simultaneously

Verification Checklist

Confirm these configurations both locally and in Play Console:

build.gradle:

android {
    compileSdkVersion 33
    defaultConfig {
        minSdkVersion 24
        targetSdkVersion 33  // Must be >= 33
    }
}

In Play Console:

1. No active bundles targeting SDK < 33
2. All testing tracks use updated bundles
3. Paused tracks contain no active bundles

Troubleshooting Persistent Warnings

If the alert remains after updates:

• Wait 2-4 hours - Propagation delays are common
• Click on the warning in your Dashboard or Policy status sections
• Ensure all track updates passed review successfully
• Use App Bundle Explorer to double-check for residual old bundles

If unresolved: Contact Google Play Support directly with evidence of API 33 compliance.