Theme
Checking connection status
Statuses appear in the Apple and Google cards on the “Distribution” tab.
| Status | Meaning and action |
|---|---|
| Not connected | The connection is not configured or the Google user was not found. Check the email and Developer Account ID |
| Checking | Google Play verification is in progress; wait for the result |
| Invitation sent | The customer confirmed an Apple or Google invitation; the team is completing checks, or Google reports a pending invitation. Access is not yet confirmed |
| Connected | Access verification succeeded |
| Insufficient permissions | The Google user has no production release permission. Update permissions and check again |
| Invitation expired | The Google invitation or access period has expired. Renew access |
| Verification error | Read the message in the card; if the cause is unclear, send it to support |
Apple
In assisted mode, the invitation checkbox and Save and Check save a request. Our team separately accepts the invitation and checks the role. Invitation sent does not confirm signing, APNs, or build readiness.
Google Play
The first assisted save without Developer Account ID creates an Invitation sent request. Our specialist finds the ID and configures technical access. If the ID is already saved, saving again performs an API check when the server technical account is configured. In manual mode, the customer supplies the ID and service account invitation.
SiteCargo looks up the service account by email in the specified account and checks its access state and production release permission. Both account permissions and permissions for the relevant app are considered, if its package name is already set.
“Connected” does not confirm every store setting: the current automatic check does not separately verify store listing permissions, agreements, or whether the account is ready to publish.
After changing permissions, run the check again from the Google Play card. If the error persists, see Troubleshooting.
Apple credential readiness
The Apple form separately shows signing, upload and push readiness. Individual requires a ready set; certificate/profile expiry is checked again before operations. Organization retains its manual access check. All statuses and actions.