Saved Store Credentials

Reuse App Store Connect and Google Play credentials across multiple projects, import them with the Chrome Extension, and manage them from one place.

Updated 2026-04-20
4 min read

If you publish multiple apps under the same Apple or Google developer account, you do not need to re-enter credentials for each Forvibe project. Saved credentials live on your account and can be attached to any project you create.

Overview

  • Credentials are stored encrypted at rest
  • One saved credential can be attached to any number of projects
  • Supports both App Store Connect (Issuer ID + Key ID + .p8 file) and Google Play (service account JSON)
  • Manage credentials from Account > Credentials, or inline when connecting a project

Skip the manual store guides entirely: the Forvibe Chrome Extension creates the credentials and imports them for you. See the Chrome Extension auto-import guide.

Step-by-step

1

Open Account > Credentials

Go to Account › Credentials. You see a list of all saved credentials, grouped by store type.

2

Add a new credential

Click Add Credential, choose App Store Connect or Google Play, paste the values, and give the credential a label (e.g. "Indie LLC" or "Personal"). The label helps you identify it when attaching to projects.

3

Attach to a project

From Project Settings > Store Connections, click Connect and pick the saved credential from the dropdown. Forvibe verifies the credentials against the store API and discovers which apps are available on that developer account.

4

(Optional) Use the Chrome Extension instead

Prefer to skip the copy-paste step entirely? Pick Auto-import with Chrome extension in the Add Credential dialog. The extension generates the credentials in the store dashboards and sends them back to Forvibe automatically. Full walkthrough in the Chrome Extension auto-import guide.

Tips

  • Label credentials by team or developer account name, not by app - one credential usually covers many apps.
  • If you rotate an API key, edit the saved credential instead of creating a new one. All attached projects pick up the new key immediately.
  • Deleting a credential detaches it from every project that uses it. Those projects will lose store access until you attach a different credential.

Troubleshooting

  • Credential verification fails - double-check the Issuer ID and Key ID for App Store Connect (they are separate values), or verify the service account JSON has the right Play Console role for Play Store.
  • Project shows connected but store calls 401 - the API key may have been revoked from the Apple or Google dashboard. Rotate it and update the saved credential.
  • App discovery returns empty - your credential has permission to the account but no apps have been created yet. Create an app in the store dashboard first, then reconnect.

Next step: set up credentials for the store you are targeting. See the App Store Connect or Google Play setup guide.