Google Play "release does not allow any existing users to upgrade" in CI

Google Play blocked the rollout because no current user could install the new release as an upgrade. This happens when the new build narrows device support, raises minSdk above existing installs, or drops an ABI those users depend on, so Play refuses to strand them.

What this error means

supply or the Play Console fails the rollout with "You cannot rollout this release because it does not allow any existing users to upgrade to the newly added APKs." The upload succeeded; the rollout is rejected.

Google Play

[!] Google Api Error: Invalid request - You cannot rollout this release because it does
not allow any existing users to upgrade to the newly added APKs.

Common causes

minSdk or device targeting excludes current users

The new build raised minSdkVersion or tightened device targeting so existing installs no longer qualify for the upgrade.

A dropped ABI or split leaves users uncovered

Removing an ABI or a density split that current users rely on means no compatible artifact exists for them.

How to fix it

Keep coverage for existing installs

Compare the new build minSdk and ABIs against what is live.
Restore the device coverage the previous release had, or retain old version codes.
Rebuild and roll out so existing users have an upgrade path.

Terminal

fastlane supply --aab app-release.aab --track production \
  --version_codes_to_retain 1230,1231 \
  --json_key google-play-key.json --package_name com.example.app

Lower the minSdk if it was raised unintentionally

If the minSdk bump was accidental, restore the prior minimum so existing devices remain eligible.

app/build.gradle

android { defaultConfig { minSdkVersion 24 } }

How to prevent it

Avoid raising minSdk or dropping ABIs in a routine release.
Retain prior version codes so older devices keep an upgrade path.
Review device coverage diffs before rolling out.