Tasks and logs

Each upload should retain a task, not just show a temporary toast. Tasks include at least the Provider, app, package digest, current stage, progress, start/end times, and public error details.

Check the stage first

Find the last successful stage, then the next failed stage. Connection, reservation, chunk-upload, platform-processing, and review failures each require very different recovery actions.

What logs contain

Logs may include public HTTP statuses, Provider error codes, field paths, resource IDs, file checksums, and local stages. They must not include JWTs, Authorization, Cookies, .p8, Service Account private keys, full license Keys, or passwords.

Sharing troubleshooting evidence

Export the task summary and redacted logs first; avoid screenshots showing only the last line. Preserve the task ID, time range, Provider, app, and package version so the failure can be matched to the correct request evidence.

Recovery principles

If the Provider has already created a resource that cannot be duplicated, refresh remote status before retrying. Do not simply resend the same Build, version number, or an upload still being processed.