staged rollout percentage not updating on Play Console: release stuck troub

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.

Not specified by the original author.

TL;DR

Set the rollout fraction to a value Play accepts for the tracks state: greater than zero, at most one, and greater than the current fraction when updating an existing rollout, expressed as a decimal fraction rather than a percentage. API and fastlane users hit this by passing 50 instead of 0.5, or by trying to lower a rollout. Correct the value in the release configuration and resubmit; to reduce exposure, halt the rollout instead of lowering the fraction.

rollout fraction invalid - Google Play staged rollout

Use this when

• A staged rollout create or update fails with rollout fraction invalid, often through the API or supply.
• You script rollouts with percentages.
• You tried to shrink a rollout by editing the fraction down.

Not for this skill when

• The release is halted, not fraction-invalid. A halted release needs a resume call with a valid fraction.
• Console UI users typing a whole number in a percent field are fine; this error is mainly an API-shape problem.

Steps

1. Read the current release state and its existing fraction from Play Console or an API track query. Verify: the current fraction and release status are known numbers
2. Convert your intended percentage to a decimal fraction, for example 20 percent becomes 0.2. Verify: the value sits between zero and one
3. If updating, ensure the new fraction is strictly greater than the current one; if you need less exposure, plan a halt instead. Verify: the update value satisfies the increase rule, or the plan switches to halt
4. Submit the create or update through your tool with the corrected fraction. Verify: the API accepts the release and returns the new status
5. Verify in Play Console that the rollout shows the intended percentage and inProgress status. Verify: Console displays the same percentage you intended
6. Document the decimal convention in the release runbook or script comments so the next operator does not repeat the percent mistake. Verify: the runbook note exists where the rollout script lives
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

The Play Developer API models rollout as a fraction between zero and one, while humans think in percentages. Passing a percentage is off by a factor of one hundred and outside the valid range. The API also forbids decreasing a live fraction, because exposure control is meant to go through halting, which preserves the option to resume cleanly.

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

rollout fraction invalid Google Play API fix

API phrasing; convert percent to decimal. 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.

fastlane supply staged rollout fraction error

Supply phrasing; set rollout as a decimal in the track configuration. 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: updating a halted release

Resuming a halted rollout reuses the fraction rules. The resume fraction must still be valid and not lower than the halted value in some states; read the track 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.

Provenance

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

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

Thread query: Google Play staged rollout halted: "rollout fraction invalid" error troubleshooting

TL;DR: Set the rollout fraction to a value Play accepts for the tracks state: greater than zero, at most one, and greater than the current fraction when updating an existing rollout, expressed as a decimal fraction rather than a percentage. API and fastlane users hit this by passing 50 instead of 0.5, or by trying to lower a rollout. Correct the value in the release configuration and resubmit; to reduce exposure, halt the rollout instead of lowering the fraction.

Not specified by the original author.

TL;DR

Use Android vitals to find the ANR cluster driving the spike, fix the main-thread block behind it, and ship the fix as a new release while halting the bad rollout. Open the ANR detail in Play Console, read the main thread stack at the freeze point, and target the top cluster first: usually disk or network work on the main thread, a locked resource during startup, or a broadcast receiver doing heavy work. Halt the rollout so the bad build stops spreading while the fix ships.

Android vitals bad behavior warning after staged rollout: ANR rate spike how to fix

Use this when

• Play Console shows a bad behavior warning for ANR rate after a staged rollout started.
• The ANR rate crossed the vitals threshold, roughly above the daily bad behavior line shown in Console.
• A recent release added startup work, a new SDK, or changed threading.

Not for this skill when

• Crashes, not ANRs, drive the warning. Crash clusters have a different triage path in vitals.
• The spike is from a tiny install base where a handful of ANRs skew the rate. Check absolute numbers before emergency work.

Steps

1. Open Android vitals, ANRs, and sort clusters by impact for the new version only, filtering out older releases. Verify: the top ANR cluster for the affected version is identified with its share of total ANRs
2. Halt the staged rollout for the bad version in Play Console to stop exposure while you fix it. Verify: the rollout status shows halted and the percentage stops growing
3. Read the main thread stack trace in the top cluster and name what the thread was doing: IO, lock wait, binder call or framework work. Verify: the blocking activity is named from the trace
4. Find the corresponding code path and move blocking work off the main thread, add timeouts to lock waits, or defer the work until after first frame. Verify: the code change targets the traced path, not a guessed one
5. Reproduce with strict mode or a profiling run on a low-end device representative of the affected segment. Verify: the scenario no longer blocks the main thread beyond a frame budget in profiling
6. Release the fix to a small staged percentage first and watch vitals for that version daily before expanding. Verify: the new versions ANR rate stays below threshold at the initial percentage for several days
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

ANRs happen when the main thread cannot respond to input or a broadcast within Androids limits. Staged rollouts expose code to device diversity the lab never sees: slow storage, low memory and OEM framework quirks turn marginal main-thread work into freezes. vitals aggregates those freezes into clusters; the top cluster is almost always one code path, which is why cluster-first triage works.

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

ANR rate spike staged rollout fix

Rollout phrasing; halt first, fix the top cluster, re-stage slowly. 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.

Android vitals bad behavior ANR threshold

Threshold phrasing; confirm rate and absolute counts in vitals. 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: SDK-caused ANRs

If the top stack sits inside a third-party SDK initialiser, upgrade or lazy-init that SDK. You cannot edit its code, but you control when it runs. 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__bzo2hnemmwLwaCPulRJbQ

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

Thread query: Android vitals bad behavior warning after staged rollout: ANR rate spike how to fix

TL;DR: Use Android vitals to find the ANR cluster driving the spike, fix the main-thread block behind it, and ship the fix as a new release while halting the bad rollout. Open the ANR detail in Play Console, read the main thread stack at the freeze point, and target the top cluster first: usually disk or network work on the main thread, a locked resource during startup, or a broadcast receiver doing heavy work. Halt the rollout so the bad build stops spreading while the fix ships.