Connect your accounts in VULK
Where to enter your Apple and Google credentials in VULK, and how they are stored.
Connect your developer accounts in VULK
Once you have done the one-time setup on Apple and Google, connect them to VULK.
Apple App Store Connect
Open your project → Publish → App Store → Connect Apple account, and provide:
| Field | What it is |
|---|---|
| Issuer ID | UUID from App Store Connect → Users and Access → Integrations |
| Key ID | The API key's identifier (e.g. 2X9R4HXF34) |
.p8 file | The private key you downloaded once from Apple |
| Team ID | Your 10-character Apple Team ID |
VULK immediately runs a verification call against the App Store Connect
API. A green check means the credentials work. If it fails, the most
common causes are: the key role is below App Manager, the membership
lapsed, or the .p8 was pasted incompletely.
Google Play
Open your project → Publish → Google Play → Connect Google account, and upload:
| Field | What it is |
|---|---|
| Service-account JSON | The key file from Google Cloud → Service Accounts |
| Package name | The applicationId you reserved in Play Console |
VULK verifies the service account can reach the Play Developer API for your package.
How VULK stores these credentials
- The
.p8and the service-account JSON are encrypted at rest with AES-256-GCM (authenticated encryption) before they touch the database — the same mechanism VULK uses for OAuth secrets. - They are decrypted only transiently, in the build pipeline, to sign requests to Apple/Google on your behalf, with your own key.
- They are never sent to the browser, never written into generated source, and never shared between users or projects.
- You can disconnect at any time in VULK (which deletes the stored credential), and you can independently revoke the key in Apple/Google. VULK never has more access than the key you issued, and you can cut that access off unilaterally.
This is the same "bring your own developer account" model used by established build services — VULK acts as your automation, never as a shared publisher.
Next: How publishing works.