Integration

App Store Connect is how a build reaches TestFlight and App Review. You paste an API key, and the agent prepares the build and the submission.

What it does

• Uploads a build and reads its processing state back.
• Reads certificates, bundle IDs, and provisioning profiles, so a build can be signed.
• Prepares a TestFlight or review submission for you to check.
• Submits only when you tap submit. Apple requires the submission to come from you, and that can never be automated.

Connecting

Open Workspace settings, then Connections, and choose App Store Connect. Create the key in App Store Connect under Users and Access, then Integrations, and paste the issuer ID, the key ID, and the contents of the .p8 file together.

What each permission is for

• An issuer ID, a key ID, and the .p8 private key Acts on App Store Connect as that key. It must be a Team key: individual keys cannot reach the Provisioning endpoints at all, so signing does not work with one.
• A Team key reaches every app in your account Apple does not allow limiting a key to one app. This is broader than we would ask for if Apple gave us the choice, and it is worth knowing before you paste it.
• One read of your app list A single call when you paste the key, to confirm Apple accepts it.

We do not ask for your Apple ID or your App Store Connect password.

How your credentials are held

Your credential is encrypted with a key that belongs to your workspace and stored as ciphertext. It is decrypted only at the moment it is used, and never inside a sandbox where code runs. We never log it.

Removing it

Disconnect under Workspace settings, then Connections, which deletes our copy. Revoke the key in App Store Connect under Users and Access, then Integrations, which ends our access immediately.

To have everything Selfbase holds about you deleted, see data deletion.

Support

Email hello@selfbase.com. Our privacy policy and terms cover every integration.