## 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.

```text
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