You will need
- A Google Play Console developer account (US$25 once). Google verifies your identity before you can publish; organisations need a D-U-N-S number.
- A Google account for Google Cloud. The Cloud project is free and nothing in this guide incurs a charge.
- Your Android package name from Launch → App identity (for example com.yourbrand.app). Copy it rather than retyping it.
What Launch asks for
Each box in Launch, named as the form names it, where the value comes from and what it looks like.
- Android package
You choose it in Launch → App identity. Play Console asks for it when you create the app.
Reverse-DNS: lower-case letters, digits and dots, fixed after your first Android build.
com.yourbrand.app- JSON key file
Google Cloud → IAM & Admin → Service Accounts → your account → Keys → Add key → Create new key → JSON. It downloads once.
A small text file that starts with {"type": "service_account" and contains project_id, private_key and client_email.
{ "type": "service_account", "project_id": "yourbrand-apps", "private_key": "-----BEGIN PRIVATE KEY-----\n…", "client_email": "[email protected]" }
Step 1: Create the app in Play Console
Sign in at play.google.com/console and click Create app. Enter the app name as it should appear on Google Play, the package name exactly as Launch → App identity shows it under Android package, a default language, App (not Game), Free, and a contact email. Acknowledge the declarations and click Create app.
Package names are permanent and can never be reused, so copy it rather than typing it. The app's dashboard then lists the Set up your app tasks (privacy policy, app access, ads, content rating, target audience, data safety and so on). They are required before a production release; internal testing works without them, so you can do them in parallel.
- 1Create app, from the Play Console home.
- 2Package name: exactly the Android package from Launch → App identity.
- 3App, Free, the declarations, then Create app.
Step 2: Enable the Google Play Android Developer API
Sign in at console.cloud.google.com. Pick a project from the project list at the top, or create one (any name, for example yourbrand-apps). Open APIs & Services → Library, search for Google Play Android Developer API, open it and click Enable.
Do this first, in the project that will own the service account. You no longer need to link the Cloud project to Play Console; Google retired that step.
- 1Pick or create the project at the top.
- 2APIs & Services → Library; search Google Play Android Developer API.
- 3Enable, before you create the service account.
Step 3: Create the service account
In the same project open IAM & Admin → Service Accounts and click Create service account. Name it appfromshop-publisher; the email shown under the name becomes appfromshop-publisher@<your project>.iam.gserviceaccount.com. Click Create and continue, skip the optional role and user steps, and click Done.
- Service account email
[email protected]You will paste this into Play Console in step 5.
- 1IAM & Admin → Service Accounts → Create service account.
- 2Name it appfromshop-publisher; the email under it is what Play Console gets.
- 3Create and continue, skip the optional steps, Done.
Step 4: Create and download the JSON key
Click the new account's email address, open the Keys tab, click Add key → Create new key, keep JSON as the key type and click Create. The browser downloads a file named after your project; it is the only copy, and Google cannot give it to you again.
Open it in a text editor: it starts with {"type": "service_account" and contains project_id, private_key (a -----BEGIN PRIVATE KEY----- block inside a string) and client_email. Launch wants the whole file. Keep it private: whoever holds it can publish as you.
- JSON key file
{ "type": "service_account", "project_id": "yourbrand-apps", "private_key": "…", "client_email": "…" }Downloaded once. Paste the entire file into Launch.
- 1The account's Keys tab → Add key → Create new key.
- 2Key type JSON → Create.
- 3The file downloads once; Launch wants all of it.
Step 5: Invite the service account in Play Console
Back in play.google.com/console open Users and permissions, click Invite new users and paste the client_email from the key file (it ends in iam.gserviceaccount.com).
Under Account permissions tick Admin (all permissions), or at minimum View app information and download bulk reports (read-only) and Release apps to testing tracks. Those two are what Launch uses today: verifying opens and discards a draft edit on your app, and submissions upload to the internal testing track. Click Invite user.
If Launch reports insufficient permissions right after you invite the account, give Google a few minutes and verify again.
- 1Users and permissions → Invite new users.
- 2Email address: the client_email from the key file.
- 3Admin (all permissions), or the two permissions Launch uses today.
- 4Invite user.
Step 6: Verify in AppFromShop
Open Launch → Google Play, paste the whole JSON key file into the box and press Verify and save. Launch exchanges the key for a Google token, opens a draft edit on your package name to confirm that the app exists and that the account may release to it, discards the edit, and only then stores the key, encrypted.
You will see Service account verified with the account's email and whether the app was found in Play Console. If it was not found yet, finish step 1 and step 5 and verify again.
What Launch asks for
- Android package
You choose it in Launch → App identity. Play Console asks for it when you create the app.
com.yourbrand.app- JSON key file
Google Cloud → IAM & Admin → Service Accounts → your account → Keys → Add key → Create new key → JSON. It downloads once.
{ "type": "service_account", "project_id": "yourbrand-apps", "private_key": "-----BEGIN PRIVATE KEY-----\n…", "client_email": "[email protected]" }
- 1Paste the entire JSON key file.
- 2Verify and save opens and discards a draft edit on your app before storing the key.
- 3Service account verified, and whether the app was found.
Step 7: Upload the first build by hand
Google accepts automated uploads only for an app that already has one app bundle uploaded through Play Console. Press Build Android in Launch and, when it shows Built, download the .aab from the build row.
In Play Console open Test and release → Testing → Internal testing and click Create new release. Upload the .aab under App bundles, keep Google's defaults, give the release a name and roll it out to internal testing. Add yourself to the testers list to install it.
From then on every later build goes out with Submit to Play internal testing in Launch, no Play Console visit needed. Personal developer accounts created since November 2023 must also run a closed test with 12 testers for 14 days before production; see Publish to Google Play.
- 1Test and release → Testing → Internal testing.
- 2Create new release.
- 3Upload the .aab downloaded from the build row in Launch.
- 4Name the release and roll it out to internal testing.
If something is refused
The message the dashboard shows, and what fixes it.
“The current user has insufficient permissions to perform the requested operation”
The invitation in step 5 is missing, or it lacks Release apps to testing tracks. Fix the permissions in Users and permissions; if you only just sent the invitation, wait a few minutes and verify again.
“Package not found”
The app in Play Console carries a different package name from Launch → App identity, or no app bundle has been uploaded yet (step 7).
“Google Play Android Developer API has not been used in project … or it is disabled”
Do step 2 in the Cloud project that owns the service account (its id is the project_id in the key file).
“Service account JSON: not a service account key file”
Paste the entire downloaded file, from the opening { to the closing }. It must contain client_email and private_key.
Done? Go to Launch
Open your app in the dashboard, choose Launch and paste what you collected. Launch verifies it with the store before anything is stored.
Sources (console paths checked against the official documentation): Google Play Developer API: Getting started · Create and set up your app · Add developer account users and manage permissions · Set up an open, closed or internal test · Create and delete service account keys · Enabling an API
