Chrome Extension Auto-Import

Let the Forvibe Chrome Extension generate and extract your App Store Connect and Google Play credentials for you, instead of clicking through the dashboards manually.

Updated 2026-04-21
5 min read

The Forvibe Chrome Extension is a shortcut that replaces the manual App Store Connect and Google Play API key guides. Instead of clicking through Apple's or Google's dashboards, you sign in, click Auto-import in Forvibe, and the extension walks through creating the credentials and sends them back to Forvibe for you.

Overview

  • Supported stores: App Store Connect (Issuer ID, Key ID, .p8 private key) and Google Play (service account JSON)
  • Automates credential creation, not just extraction - the extension creates the API key or service account for you
  • Works for multiple developer accounts - pair once per account, the credentials land in Account > Credentials and can be attached to any project
  • You do not need to pre-create an app in the store dashboards; the extension only needs you signed into Apple Developer or Google Cloud

The extension runs on any Chromium-based browser (Chrome, Arc, Brave, Edge). It is not published on the Chrome Web Store - Forvibe distributes it directly as a ZIP that you load via chrome://extensions in Developer Mode. See the Chrome Extension install guide for the install steps.

Step-by-step

1

Install the extension

Follow the Chrome Extension install guide. It takes about two minutes: download the ZIP, open chrome://extensions, enable Developer Mode, click Load unpacked, and select the unzipped folder. Pin the Forvibe icon to your toolbar so the pairing fallback is always one click away.

2

Open the Credentials wizard in Forvibe

Go to Account › Credentials and click Add Credential. Pick App Store Connect or Google Play. In the dialog, choose Auto-import with Chrome extension.

3

Pair the extension

Forvibe displays a 6-character pairing code and detects whether the extension is installed. In most cases the extension picks the code up automatically and opens a new tab. If nothing happens, click the Forvibe extension icon in your toolbar and paste the 6-character code manually.

4

Sign in and follow the overlay

The extension opens the right destination - App Store Connect Keys page for ASC, or Google Cloud Console Service Accounts page for Play. Sign in if you are not already. An overlay wizard walks you through any remaining clicks: confirming the key name, picking a service account, downloading the file. The extension captures the .p8 or JSON download and extracts the Issuer ID / Key ID automatically.

5

Credentials land in Forvibe

When extraction finishes, the overlay closes and Forvibe shows the new credential in Account > Credentials. From there, attach it to any project from Project Settings > Store Connections. You can remove the extension after this point - credentials are stored on Forvibe, not in the extension.

What happens behind the scenes

The pairing code flow is simple: Forvibe generates the code and talks to the extension through Chrome's externally_connectable messaging channel. The extension exchanges the code for a short-lived bearer token, opens the correct store tab, runs the overlay wizard, and sends the extracted credentials back to Forvibe's save-credentials endpoint. Credentials travel encrypted in transit and at rest - your source code and API keys never touch the extension's local storage long-term.

Fallbacks

  • Extension not auto-opening after you click Auto-import - click the Forvibe icon in your toolbar and paste the 6-character pairing code
  • Automated extraction failed partway (e.g. download was blocked) - drop the .p8 or service account JSON file into the drop zone shown in the overlay, and the extension finishes the flow with the file you provide
  • Extension not installed or won't detect - the wizard falls back to the manual guides: App Store Connect setup and Google Play setup

Tips

  • If you manage multiple Apple or Google developer accounts, run the pairing flow once per account. Label each credential with the team name so you can tell them apart when attaching to projects.
  • Newly created API keys take about 15 seconds to propagate on Apple's side; Google service account keys take 30-60 seconds. Forvibe retries transparently - give it a minute before assuming something is broken.
  • You can uninstall the extension right after credentials are saved. The extension holds nothing long-term; Forvibe owns the stored credentials from then on.
  • Sign into Apple Developer / Google Cloud in the same Chrome profile you use for the extension. The extension cannot reach tabs in other profiles.

Troubleshooting

  • Forvibe says extension not detected - refresh the Forvibe tab. Chrome caches the externally_connectable list and a reload forces it to re-read.
  • Pairing code expired - codes are short-lived. Close the dialog in Forvibe and click Auto-import again to get a fresh code.
  • Overlay never appeared on the store page - the extension icon in your toolbar should turn active. Click it and paste the code manually if it did not pick up automatically.
  • Credential saved but Forvibe rejects it - the key may still be propagating. Wait 60 seconds and hit Verify on the credential row.
  • Safari / Firefox - not supported. The extension relies on Chromium's externally_connectable API.

Next step: attach the new credential to a project. See the saved credentials guide.