Troubleshooting

Connection failure

Check the credential type, whether IDs belong to the same account context, private-key format, and local time. If a network proxy is enabled, also check its address, TLS root certificates, and DNS.

Can read but cannot write

Reading an app only proves the credentials are valid. Check target-app permissions, Provider roles, agreement status, and specific resource permissions required by the operation. Do not hide permission-model problems by granting global administrator access.

Preflight failure

Use the package's actual Info.plist, manifest, signature, and Profile. Filenames, build-script output names, and handwritten records cannot replace facts inside the package.

Upload failure

Distinguish reservation, chunk upload, checksum, confirmation, and platform processing by task stage. Preserve public error codes and field paths. Do not send Authorization, Cookies, full Keys, or private keys in chats or support tickets.

Platform processing takes too long

Refresh the remote Build/package status to check whether it is still processing or has failed. Do not upload the same version again just because the interface has not changed for a short time.

Still unable to identify the issue

Prepare the Provider, app, package version, task ID, time, last successful stage, and redacted logs. Complete context is more likely to produce an accurate answer than “upload failed.”