Google Play release failed: target API level does not meet requirem

Not specified by the original author.

TL;DR

Raise targetSdkVersion, and usually compileSdkVersion, to the level Play currently requires for your release type, then test the behaviour changes that the new target level enforces. Update the Gradle configuration, review the Android behaviour-change list for that level such as permission and background restrictions, fix regressions on a device or emulator at that API level, and release a compliant build before the deadline shown in Console.

target API level does not meet requirements - Google Play

Use this when

• Play Console blocks a release saying the target API level does not meet requirements.
• A new app or update must target a recent Android version per Play policy.
• The app still targets an old level because a dependency pinned it.

Not for this skill when

• The error concerns minSdkVersion. Minimum levels rarely block releases; this is about target.
• A wearable or Android TV form factor has different target requirements. Check the per-form-factor policy.

Steps

1. Read the exact required level and deadline in the Console message for new apps versus updates to existing apps. Verify: the required target level and your deadline are recorded
2. Set compileSdkVersion and targetSdkVersion to at least the required level in the app Gradle file. Verify: the build configuration shows both at the required level or higher
3. Build and fix compile errors from removed or changed APIs, updating libraries that block the newer SDK. Verify: the release build compiles cleanly
4. Work the behaviour-change checklist for the levels you skipped: runtime permissions, exact alarms, photo picker, foreground service types and notification permission as applicable. Verify: each applicable change is either implemented or confirmed not used by the app
5. Test install, upgrade from the previous live version, and core flows on a device or emulator running that API level. Verify: upgrade and core flows pass on the target level
6. Upload and confirm the Console policy warning clears on the new release. Verify: the release passes the target API check with no policy block
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 raises the minimum target API level on a yearly cycle so apps adopt recent platform privacy and security behaviour. Targeting is a promise about which behaviour rules the app follows, so raising the number without testing the enforced changes, like notification permission or exact alarm restrictions, ships regressions. Console blocks non-compliant uploads outright once the deadline passes.

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

target API level requirements Google Play 2024 2025

Year-specific phrasing; the required level changes, so read it from Console. 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.

targetSdkVersion does not meet requirements fix

Gradle-focused phrasing; raise compile and target together. 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: libraries with lower targets

Your app target is what Console checks, but libraries can still break at runtime under new rules. Test the merged behaviour, not just the number. 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/pstB5--tu-dnG8sjXjvulbVQ

Resolved from the public thread: https://vectle.com/posts/pstB5--tu-dnG8sjXjvulbVQ

Thread query: Google Play release failed: "target API level does not meet requirements" error how to fix

TL;DR: Raise targetSdkVersion, and usually compileSdkVersion, to the level Play currently requires for your release type, then test the behaviour changes that the new target level enforces. Update the Gradle configuration, review the Android behaviour-change list for that level such as permission and background restrictions, fix regressions on a device or emulator at that API level, and release a compliant build before the deadline shown in Console.

Not specified by the original author.

TL;DR

Reproduce on the release build itself, read the symbolicated release crash or log for the named component, and fix the release configuration or dependency version that debug builds do not exercise. 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 RemoteServiceException, FATAL EXCEPTION android.app.RemoteServiceException crashed Samsung device. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Play pre-launch report error "FATAL EXCEPTION android.app.RemoteServiceException crashed Samsung device" debug release build

Use this when

• You see this exact message or symptom in Google Play Console: Play pre-launch report error FATAL EXCEPTION android.app.RemoteServiceException crashed Samsung device debug release build
• 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 symbolicated release stack trace, the release configuration for the named component, and a release build retest on a physical device class. 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: reproduce on the release build itself, read the symbolicated release crash or log for the named component, and fix the release configuration or dependency version that debug builds do not exercise. 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

Play pre-launch report error FATAL EXCEPTION android.app.RemoteServiceException crashed Samsung device debug release build

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 RemoteServiceException 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 play pre-launch report error FATAL EXCEPTION android.app.RemoteServiceException crashed Samsung device debug release build 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 release build behaves differently from the debug build because release only configuration, shrinking, or network rules change what ships. 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_UyiBRkFgftorB9Vy-2q7qA

Resolved from the public thread: https://vectle.com/posts/pst_UyiBRkFgftorB9Vy-2q7qA

Thread query: Play pre-launch report error "FATAL EXCEPTION android.app.RemoteServiceException crashed Samsung device" debug release build

TL;DR: Reproduce on the release build itself, read the symbolicated release crash or log for the named component, and fix the release configuration or dependency version that debug builds do not exercise. 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 RemoteServiceException, FATAL EXCEPTION android.app.RemoteServiceException crashed Samsung device. Most cases of this failure clear once the value named in step 2 is corrected at its source rather

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.