Connect your Google Play account

Create the app in Play Console, a service account that can publish for you, verify it in Launch, and plan for the 12-tester rule.

Updated November 12, 2026Launch and publish

Your Android app is published under your Google Play developer account. Here is the one-time setup.

What you need

  • A Google Play Console developer account (US$25 once; Google verifies identity, which can take a few days) and a Google Cloud project, which is free.
  • About 20 minutes and the Android package name from Launch → App identity (for example com.yourbrand.app).

Step 1: Create the app in Play Console

play.google.com/console → Create app: the app name, default language, App, Free, and the declarations. The package name is fixed by the first upload, so it must match Launch exactly.

Before a public release Google also requires the Set up your app checklist: privacy policy URL, app access, ads, content rating questionnaire, target audience and data safety. Internal testing works without it, so you can do this in parallel.

Step 2: Create a service account

console.cloud.google.com → pick or create a project → APIs & Services → Library → enable Google Play Android Developer API.

IAM & Admin → Service Accounts → Create service account, name it appfromshop-publisher, finish without roles. Open it → Keys → Add key → Create new key → JSON. The file downloads once; keep it private.

Step 3: Invite it to Play Console

Play Console → Users and permissions → Invite new users → paste the service account's email address (it ends in iam.gserviceaccount.com). Under Account permissions grant Admin, or at minimum Release to testing tracks, Release to production and View app information. Send the invitation; it is active immediately.

Step 4: Verify in AppFromShop

Launch → Google Play → paste the JSON key file's contents → Verify and save. We obtain a token from Google and probe your app before storing the key encrypted.

Step 5: The first upload is manual

Google only accepts automated releases after the first app bundle has been uploaded through Play Console by hand. When your first Android build finishes in Launch, download the .aab and upload it once under Testing → Internal testing → Create new release. Every later submission runs from the dashboard.

The 12-tester rule for personal accounts

Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers, opted in continuously for 14 days, before an app can go to production. Organisation accounts are not covered by this rule.

Start the closed test as early as you can: invite 15 to 20 people (friends, family, staff) so a few drop-outs don't reset you, and make sure each tester opens the opt-in link with their Google account and installs the app from Google Play. Design changes reach the testers' apps without new uploads, so keep improving the app during the 14 days.

Frequently asked questions

"The current user has insufficient permissions"

The invitation in step 3 is missing or lacks release permissions.

"Package not found"

The app in Play Console uses a different package name, or step 5 has not happened yet.

"API not enabled"

Enable Google Play Android Developer API in the Cloud project that owns the service account.

Do I need Firebase for Android push?

No. Android push runs on Firebase projects AppFromShop owns; there is nothing to create or upload on your side.

Was this article helpful?Your answer helps us decide what to improve next.

Still need a hand?

Open a ticket and a person from the AppFromShop team replies by email, usually within one business day. Signed in, your workspace and app come attached so we can start straight away.