Home / Guides / Release updates
GOOGLE PLAY RELEASE GUIDE · REVIEWED OCT 2026

Google Play update failing? Compare version codes and signing first.

Update failed or version code rejected? Check the basic build requirements before investigating policy.

If an update will not upload or is rejected during release preparation, the first task is to separate a build-identity problem from a policy or review problem. A new release must preserve the application identity while moving its version code forward. Do not assume every rejection is caused by a version code.

What matters

  • For a normal app update, Google Play requires the updated bundle to use the same package name, a greater version code, and the correct signing identity.
  • The human-readable versionName is not a substitute for versionCode. A version name can look newer even when the numeric code is not.
  • Changing code alone will not resolve a policy rejection; compare the Play Console message with the changed release fields.

Step-by-step investigation

1. Record the baselineRecord the last accepted release’s package name, versionCode, versionName, signing information, and track. Use actual build or Play Console evidence, not memory.
2. Check the candidateVerify the candidate bundle has the same package name, its versionCode is strictly greater, and the applicable signing identity is correct.
3. Compare what changedList new permissions, SDKs, sensitive features, store declarations and reviewer-access behavior. Keep technical upload failures separate from review findings.
4. Match the error to evidenceIf an upload fails, follow the exact Console validation message. If it reaches review and is rejected, read the policy notice and inspect the affected feature and declaration.
5. Retest before resubmittingRebuild with the intended configuration, test install/update behavior and verify the release metadata before uploading again.

A worked example (synthetic)

Example: versionCode did not increase

Previously accepted: package com.example.notes, versionCode 120. Candidate: same package, versionCode 120. This is a confirmed input conflict for a normal update because the candidate code has not increased. A comparison tool can flag the mismatch; it cannot verify your actual signing certificate.

Compare the previous and candidate releases

Keep a record of what you actually know. In the free browser tool, enter a verified previous-release snapshot and candidate-release snapshot. Run the comparison to inspect changed fields and export a report. Unknown information should stay unknown.

Use the release comparison tool

No account or real release required to try a sample. Your entered snapshots are processed in your browser.

Open free comparison tool →

What this guide cannot verify

A snapshot comparison cannot inspect the AAB signing certificate, confirm which track is currently live, or determine the private cause of a Play review decision. Google Play Console remains the source of truth.

Official documentation

Editorial note: Content checked against the linked official sources on October 28, 2026. This independent guide is informational, not legal advice or a guarantee of Google Play approval.