Fix Google Play bundle and version-code errors

Play rejected the bundle before you could move on with the release. The error tells you what to check: package identity, signing, version code, or compatibility. We’d read that message before rebuilding, so the next upload addresses the actual problem.

Keep the bundle filename, package name, version code, expected upload certificate, and full console message. Make sure you’re in the intended app and track.

Match the error to the fix

Wrong app or package name

Compare the bundle’s application ID with the Play app. Package names are unique and permanent. Changing the display name won’t change the package identity.

Don’t rename an existing app’s package to get an update accepted. That creates a different app identity and won’t update installed copies.

Version code already used

Build again with a valid, unused version code for the update path. The numeric version code is separate from the version name users see.

Incorrect signing key

Compare the upload certificate with the key Play expects. If you’ve lost the upload key, use the supported reset process.

Target API or compatibility error

Find the dependency or build setting responsible, then follow the build requirements.

Create release is disabled

Check unfinished app-setup tasks and existing draft releases. Complete or resolve the relevant work before starting another release.

Check the release after the upload succeeds

Add release notes, review the release, and fix blocking errors before continuing. A warning and a blocking error don’t mean the same thing.

You’re ready for the next step when Play accepts the bundle into the intended release and allows the next review or rollout action. Saving an accepted bundle doesn’t necessarily send the release for review.

If you need your build provider’s help, send the error and non-secret build identifiers. Keep private signing files out of the request.