Codemagic Play publishing failed Google Play edit was not committed, t

Not specified by the original author.

TL;DR

Look the object up by listing the current workspace rather than trusting the stored id or name, remap the reference to the current id, and fail loudly when a listing has no match. Start in the Play Console release page, the app bundle explorer, and the policy status page, work on one affected item, and prove the fix there before running the full set. The named signal in this one is Google Play edit was not committed, track production does not exist. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Codemagic Play publishing failed "Google Play edit was not committed, track production does not exist"

Use this when

• You see this exact message or symptom in Google Play Console: Codemagic Play publishing failed Google Play edit was not committed, track production does not exist
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Google Play Console fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Play Console release page, the app bundle explorer, and the policy status page and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the release track, the bundle signing key, the declarations for the release, and the target API level in the bundle, and check the current listing of the named objects, the old versus new id or name, and the remapped reference in the config. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: look the object up by listing the current workspace rather than trusting the stored id or name, remap the reference to the current id, and fail loudly when a listing has no match. Verify: the corrected value or setting is visible in Google Play Console itself, not only in a local config file
4. Re-run the original operation on the single affected item first: correct the named item, create a new release on an internal track first, and check the release summary before promoting it. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the internal release saving without the error and the bundle explorer showing the corrected values. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Codemagic Play publishing failed Google Play edit was not committed, track production does not exist

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Google Play Console Google Play edit was not committed, track production does not exist during the run

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does codemagic Play publishing failed Google Play edit was not committed, track production does not exist keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Google Play Console, Android App Bundles, Play App Signing, current target API requirements. The steps assume you can read the job or build log and change the named object in Google Play Console.

Why it happens

In Google Play Console, this failure usually means the reference the job uses points at an object that was renamed, merged, moved, or never created in this workspace, so the lookup returns nothing. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_hXbrEYYMbKGxqKijfKfkPg

Resolved from the public thread: https://vectle.com/posts/pst_hXbrEYYMbKGxqKijfKfkPg

Thread query: Codemagic Play publishing failed "Google Play edit was not committed, track production does not exist"

TL;DR: Look the object up by listing the current workspace rather than trusting the stored id or name, remap the reference to the current id, and fail loudly when a listing has no match. Start in the Play Console release page, the app bundle explorer, and the policy status page, work on one affected item, and prove the fix there before running the full set. The named signal in this one is Google Play edit was not committed, track production does not exist. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Supply the exact keystore credentials the file was created with, checking for whitespace, wrong variable mapping and a corrupted upload in Codemagic code signing settings. This Java keytool message appears both for a genuinely wrong store password and for a damaged or re-encoded keystore file. Re-upload the original binary keystore, re-enter its credentials as CI variables without copying stray characters, and verify locally with keytool before rebuilding.

keystore was tampered with or password was incorrect - Codemagic

Use this when

• Codemagic Android signing fails with this keytool message.
• Credentials were moved from another CI or retyped by hand.
• The keystore was stored as text, for example base64 handled incorrectly, at some point.

Not for this skill when

• The alias password differs from the store password and only the alias is wrong. keytool messages blur the two; test both locally.
• The keystore is the wrong file entirely, such as a debug keystore. Verify fingerprints.

Steps

1. Download or locate the original keystore file and test it locally with keytool list using the credentials you believe are correct. Verify: keytool lists the alias locally, proving file and credentials, or fails identically proving one is wrong
2. Compare the fingerprint Codemagic reports or the uploaded file size against the known-good local file. Verify: file sizes and fingerprints match, or the uploaded copy is confirmed corrupt
3. Re-upload the keystore to Codemagic as a binary file, never via a text field that could alter bytes. Verify: the code signing settings show the re-uploaded keystore
4. Re-enter the store and key passwords in Codemagic variables by typing rather than pasting from a document that may add spaces. Verify: variables are saved and masked in the UI
5. Check the workflow references the correct keystore entry name and alias. Verify: the workflow signing section names the same entry and alias as keytool lists
6. Rebuild in Codemagic. Verify: signing completes and the release AAB is produced
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

keytool cannot distinguish a wrong password from file corruption because both fail the integrity check the password provides. CI migrations introduce both: passwords gain trailing spaces through spreadsheets, and keystores get mangled when they pass through text-oriented secret stores. Local keytool verification separates file health from credential health before touching CI again.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

Codemagic keystore tampered password incorrect fix

CI phrasing; re-upload the binary and re-enter credentials. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

keytool keystore was tampered with or password was incorrect

Tool phrasing; test the file locally with keytool list first. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: JKS versus PKCS12 format

Newer keytools default to PKCS12. A format mismatch with old tooling can mimic corruption; check the format flag when listing. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_1Q2QyvU3eItyu1JjKsV5sw

Resolved from the public thread: https://vectle.com/posts/pst_1Q2QyvU3eItyu1JjKsV5sw

Thread query: Codemagic build failed: "keystore was tampered with or password was incorrect" error

TL;DR: Supply the exact keystore credentials the file was created with, checking for whitespace, wrong variable mapping and a corrupted upload in Codemagic code signing settings. This Java keytool message appears both for a genuinely wrong store password and for a damaged or re-encoded keystore file. Re-upload the original binary keystore, re-enter its credentials as CI variables without copying stray characters, and verify locally with keytool before rebuilding.

Not specified by the original author.

TL;DR

Check whether the release was halted, the update is still propagating, or you are editing a superseded release: read the release status on the track page, confirm the new fraction saved, and remember Console percentages reflect the target fraction while actual device reach lags by hours. If the release status shows halted, resume it; if a newer draft release replaced yours, work on the live one. Verify with the track details API or the releases overview rather than refreshing the same page.

staged rollout percentage not updating on Play Console: release stuck

Use this when

• You raised the rollout percentage but Console or devices show no change.
• A teammate may have halted the release after a bad signal.
• Multiple draft or active releases exist on the same track.

Not for this skill when

• The percentage updated but users report not seeing the update. That is propagation and Play update checks, a different timeline.
• The release was rejected by policy review. Then the release page shows a review block, not a percentage problem.

Steps

1. Open the production track and read the live releases status, fraction and last modified time. Verify: the current status, fraction and timestamp are recorded
2. Check the release history or audit view for a halt, edit or replacement by another team member or an API call. Verify: any state change after your edit is identified
3. If halted, review the vitals or crash reason for the halt, then resume the rollout at the intended fraction if it is safe. Verify: the release status returns to inProgress at the intended percentage
4. If you edited a draft while another release is live, discard or merge the draft and edit the live release instead. Verify: only one active release carries the rollout and it shows the right fraction
5. Confirm the change through an API track query or the releases overview page, which can be fresher than a cached release page. Verify: a second view agrees with the intended percentage
6. Wait a few hours and sample real device reach through vitals adoption for the version before declaring it stuck. Verify: adoption data moves in line with the new fraction over the following day
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

Play rollout state is a server-side release object that several people and automations can touch. Halts, superseding drafts and plain UI caching all present as the percentage not updating. The release object itself, read through the track view or API, is the only reliable truth; adoption on devices always trails the setting by design.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

Play Console rollout stuck percentage fix

Direct phrasing; check halt state and superseding releases. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

staged rollout halted vs not updating

Diagnostic phrasing distinguishing a halt from a display lag. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: managed publishing

With managed publishing on, saved changes queue until someone publishes them. The percentage will not move until the queued changes go live. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_W-h5zKqpBqYNDc5adTPMHA

Resolved from the public thread: https://vectle.com/posts/pst_W-h5zKqpBqYNDc5adTPMHA

Thread query: staged rollout percentage not updating on Play Console: release stuck troubleshooting

TL;DR: Check whether the release was halted, the update is still propagating, or you are editing a superseded release: read the release status on the track page, confirm the new fraction saved, and remember Console percentages reflect the target fraction while actual device reach lags by hours. If the release status shows halted, resume it; if a newer draft release replaced yours, work on the live one. Verify with the track details API or the releases overview rather than refreshing the same page.