Common Google Play errors

Solution

Please make sure you have done the following:

1. Created a service account in the Google Play console
2. Set the service account access to Service Account User
3. Created a JSON private key
4. Added the JSON key to Codemagic
5. Navigated to your Google Play Console API access and granted access to the service account
6. Given the service account access to your application
7. Invited users to the service account

Checkout this guide for codemagic.yaml or this guide for Workflow editor.

Solution

• Try setting admin access for Account permissions on google play console.
• After granting access, Google may take 24-48 hours to propagate all access rights for all APIs or new users.

Solution

Use set cancel_previous_builds: true in your triggers, but it doesn’t work when builds are triggered using API.

Solution

Try to upload .aab by incrementing the version code.

Solution

Check version and version code.

Solution

You can change its track or increment the version code.

Solution

You will have to update your app accordingly to be able to publish to Google Play Store.

Solution

Check your version code and upgrade it to a higher version code.

Cause

This happens when either, you haven’t uploaded the first artifact to your Google Play application manually, or the generated artifact package name has some suffixes or changes and doesn’t correspond to the one in Google Play.

Solution

Ensure the package name matches exactly with the one in Google Play, or upload the first artifact manually to create the application.

Solution

Check code signing. Use the same keystore while uploading your artifacts.

Solution

Enroll your app into app signing by Google Play to have Google sign the .aab that are generated from the app bundle during installation.

Solution

Set your signing configuration in build.gradle in release mode. Refer to this for more information.

Solution

You should use ./gradlew bundleRelease to generate .aab file. And don’t forget to mention the artifact path app/build/outputs/bundle/**/*.aab in the artifacts: section in your codemagic.yaml.

Solution

In case you want to upload the artifacts generated in the build to Google Play as a draft release, select Submit release as draft in the workflow editor or submit_as_draft: true in your yaml configuration.

Solution

• Beware, this parameter should not always be true.
• If an app/track is in a “rejected” state, then you need to submit the app with changesNotSentForReview: true, otherwise, you should send without specifying changesNotSentForReview(or setting it to false).

publishing:
  google_play:
    credentials: $GOOGLE_PLAY_SERVICE_ACCOUNT_CREDENTIALS
    track: internal
    # Optional boolean To be used ONLY if your app cannot be sent for review automatically
    changes_not_sent_for_review: true

• If you are getting a 400 error related to the app being in draft status, either enable publishing to draft by setting the value of submit_as_draft to true or promote the draft build up by a level to one of the testing tracks. Play Console will show you how to do this. You’ll need to go through the steps, fill out questionnaires, upload various screenshots, and then after approval, you can move to the Alpha testing track, and Codemagic will successfully publish.
• Depending on your app’s update status, it may not be sent for review automatically.
• If your changes are sent to review automatically, but the field is still set to true, you may get the error Changes are sent for review automatically. The query parameter changesNotSentForReview must not be set.
• Also, it might be that the actual cause of the error is getting swallowed and is surfaced by changesNotSentForReview error. In that case, try to re-run it by adding --stacktrace that will print out a full stack trace.
• Check this out.

Solution

The solution is to try again after some time.