You Uploaded an Apk That Is Signed With a Different Certificate to Your Previous Apks.
Your APK is using permissions that require a privacy policy
A privacy policy has to be added both in your app and on the store listing of your Google Play console to be compliant with Google's near recent guidelines.
To do so, follow the steps explained here: Google Play - Privacy Policy
You need to apply a different version code for your APK
This message means you accept already uploaded this version but never published it.
Before uploading the same version lawmaking APK file in your Google Play console, remove the latest APK uploaded to the release.
1 - GoRelease management > App release > Edit Release
2 - ClickRemove next to the latest APK you take uploaded and clickSave at the bottom of the page
three - Go toArtefact library and delete the APK previously uploaded
4 - Get back toRelease direction > App release > Edit Release and upload the new APK.
You uploaded an APK that is signed with a dissimilar certificate to your previous APKs
This message means that you are trying to update an existing app created with some other service than GoodBarber
If so, y'all must upload an APK file that contains the aforementioned document. To learn more, go to this page: Update an existing app created out of GoodBarber.
There are 3 possibilities:
#ane - Y ou don't have the .keystore file -GoodBarber cannot retrieve information technology for yous. Then, your app must be published as a new app on the Google Play console.
#2 - Yous ain the .keystore file - If so, follow these steps:
one - Ask the support to set you back at the get-go of the Android publication procedure.
ii - In your GoodBarber dorsum office, go to Publish > Android App > Publish
3 - Select the third option - This version is an update of an app created with some other platform than GoodBarber and add the.keystore file of your existing app, plus the associated countersign. Click next step.
4 - At step 2, add the packet name of the app already published on the store. Click next step until Step 6
five - Go to your Google Cloud Console > APIs and Services > Credentials > Select the Android cardinal
vi - Make certain the bundle proper name and the
SHA-1 certificate fingerprint matches the ones provided in the back office at Step half-dozen.
7 - Go back to your GoodBarber back office and Click next step
8 - Click build my application
nine - Once the app built, download the APK file and upload it to the Google Play panel.
#3 - You had already chosen the 3rd option and uploaded a . keystore file - this ways that the .keystore file uploaded was not the right one.
Target API level requirements
Our apps are optimized for this in our recent builds. Any Android app built afterward release #5720 is updated to API level 27. Yous can check this information here .
Side by side steps:
1 - Ask the support to unlock your back office so yous tin rebuild your app
2 - In your Google Play console, go to Release management > App release > Edit Release
three - Click Remove adjacent to the latest APK you have uploaded and click Salve at the bottom of the page
four - Go to Artefact library and delete the APK previously uploaded
5 - Go dorsum to Release direction > App release > Edit Release
6 - Upload the new APK
Device back up removed
This warning message means that the latest updated Google services are no longer compatible with very old phones. The previous version was compatible with more than devices than the new one.
Source: https://www.goodbarber.com/help/publication-and-updates-of-the-android-app-r99/android-apk-upload-failed-and-warning-messages-on-google-play-a336/
0 Response to "You Uploaded an Apk That Is Signed With a Different Certificate to Your Previous Apks."
Post a Comment