Overview

When uploading your MACS Android APK file to Google Play Store you may receive an error saying "You uploaded an APK or Android App Bundle that is signed with a key that is also used to sign APKs that are delivered to users". This article explains why this occurs and what steps you can take to resolve it. 

Diagnosis

You may receive the following error messages when trying to upload an APK file you received in the automated MACS email after submitting the app on the MACS CMS platform.

Upload Failed

You uploaded an APK or Android App Bundle that is signed with a key that is also used to sign APKs that are delivered to users. Because you are enrolled in App Signing by Google Play, you should sign your APK or Android App Bundle with a new key before you upload it. 

mceclip0.png

 This error is usually the result of enrolling for Google Play App Signing when initially uploading the APK. It is received as the certificates from the existing app do not match the app (APK) that you want to upload. This would generally occur:

  • when the Google Play App signing option has been used for this app or
  • if the app is created on another App Builder

In the case of MACS it is usually because of the signing option that has been enabled.

Prerequisites

  • APK file you received in the automated email after submitting the file on the CMS platform

Solution

As a workaround, you should NOT use Google Play App Signing while publishing an app.

If the app is not live yet, you could delete the listing and start from scratch.

  1. Log into your Google console and go to All Applications.
  2. Click on the respective app that you'd like to delete.
  3. Look at the very top where your app name is located. If your app says DRAFT, right next to it is the Delete button.

Alternatively, if you want to keep the existing upload and remove it only once the new one is published, follow the steps as outlined in the Disabling Google Play App Signing while publishing an app KB article.