Google Play API credentials

The portal uses a service-account JSON file to upload builds to Google Play. This is the Google Play API credential requested on the App Store page. Start with your App Name and App Identifier, then add this file if you want store uploads. See the mobile setup checklist.

1. Create the service account

Use a Google Cloud project controlled by your organisation and the Play Console account that will publish the app.

1. Open Google Cloud Console  and select an existing project, or create one for your Play integration.
2. Open APIs & Services → Library, find Google Play Android Developer API, and enable it.
3. Open IAM & Admin → Service Accounts → Create service account.
4. Give it a name such as SessionCloud Play uploads, finish creation, and copy its email address ending in iam.gserviceaccount.com.

Play permissions are granted in Play Console in step 3 below; a Google Cloud Owner or Editor role on the service account is not needed for store uploads. Google no longer requires linking the Play developer account to the Cloud project. See Google’s Play API setup instructions .

2. Download the JSON key

1. Open the service account in Google Cloud Console.
2. Select Keys → Add key → Create new key.
3. Choose JSON, then Create, and keep the downloaded file securely.

If key creation is disabled by your organisation, ask your Google Cloud administrator to arrange the permitted credential setup. See Google’s service-account key instructions .

3. Give it access to your Play app

1. Sign in to Google Play Console  as the account owner or an administrator.
2. Create the app’s Play Console record if necessary and complete its required initial setup.
3. Open Users and permissions, add a user, and enter the service-account email copied earlier.
4. Under App permissions, add the app this portal project will upload to. Grant View app information (read-only) and Release apps to testing tracks, then save/invite the service account.

Access to the chosen app and testing releases is sufficient for this portal’s Internal testing draft workflow; production-release and financial permissions are not required. Permissions in Google Cloud and Play Console are separate. See Google’s Play Console permissions guide .

4. Save it in SessionCloud

1. Open your project’s App Store → Android → Google Play uploads section.
2. Select the downloaded file in Google Play service-account JSON.
3. Click Save Google Play credentials and wait for the saved confirmation.

Use the same Android package identifier as your Play app. The portal uses the main App Identifier unless Advanced: Android release version and identifier contains an Android override. For an existing published app, preserve its identifier and signing key.

Saving the JSON validates and stores the credential; Google Play access is checked when an upload runs.

5. Upload a successful build

Create a new Android build after completing setup. In Build History, click Upload to Google Play beside the successful build. SessionCloud uploads that build’s Android App Bundle as an Internal testing draft. Review and publish the draft in Play Console when ready.

An older build may say Create a new build because it has no separately saved app bundle. Building does not automatically upload to Google Play; you choose which successful build to upload.

Store listings, app-signing enrollment, declarations and review requirements still need to be completed in Play Console. See Google Play Store Approval.

Google Play JSON and Firebase JSON

No Firebase account setup or manual Firebase JSON upload is needed for a new app. Your personal Google username and password are not used for these uploads.