我如何解决后续的.apk上传证书与原始证书不同的问题 [英] How do I resolve the issue where subsequent .apk upload certificate differs from the original

问题描述

我正在尝试将新的.apk文件上传到Google Play开发者控制台中的Open Testing，但出现此错误:

I'm trying to upload a new .apk file to Open Testing in the Google Play Developer Console and I'm getting this error:

You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint:
    SHA1: key:key:key
    and the certificate used to sign the APK you uploaded has fingerprint:
    SHA1: a:diff:key
    Your APK or Android App Bundle is using permissions that require a privacy policy: (android.permission.GET_ACCOUNTS). Learn More

我正在生成具有以下内容的密钥:

I'm generating keys with the following:

ionic cordova build android --prod --release

来自android版本目录. keytool -genkey -v -keystore my-release-key.keystore -alias my_app -keyalg RSA -keysize 2048 -validity 10000

From android release dir. keytool -genkey -v -keystore my-release-key.keystore -alias my_app -keyalg RSA -keysize 2048 -validity 10000

版本dir中的jar签名者 jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore my-release-key.keystore app-release-unsigned.apk my_app

Jar signer from release dir jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore my-release-key.keystore app-release-unsigned.apk my_app

从发布目录最后一次zip对齐 /Users/anonymous/Library/Android/sdk/build-tools/30.0.3/zipalign -v 4 /Users/anonymous/project/my-app/platforms/android/app/build/outputs/apk/release/app-release-unsigned.apk MyApp.apk

Lastly zip align from release dir /Users/anonymous/Library/Android/sdk/build-tools/30.0.3/zipalign -v 4 /Users/anonymous/project/my-app/platforms/android/app/build/outputs/apk/release/app-release-unsigned.apk MyApp.apk

我删除了旧的密钥库文件，所以这是一个新文件.我不确定如何在PlayStore上解决此问题.

I deleted the old keystore file so this is a new one. I'm not sure how to resolve this on PlayStore.

我已经搜索过，但是找不到适合我的解决方案.我不确定该如何处理不匹配的密钥库文件，假设这是问题所在，而根据我的研究，听起来这就是问题所在...我正在使用其他密钥库文件.我一直在寻找一种方法，无法将Playstore中的密钥重置为无效.

I've searched but I can't find a solution that works for me. I'm not sure what to do about the mismatched keystore file, assuming that's the issue and from my research it sounds like that's the issue...I'm using a different keystore file. I've searched for a way to reset the key in Playstore to no avail.

任何帮助将不胜感激.

推荐答案

您可以在此问题上与Google Play控制台支持联系，他们将可以手动将密钥库重置为新的密钥库，因为您无济于事在控制台中.

You can contact Google Play Console Support on this issue and they will be able to reset the keystore to your new keystore for you manualy as there is no way to do this in the console.

在播放控制台中，点击顶部的帮助按钮>向下滚动以获取更多帮助，然后单击联系我们" >输入您需要帮助的密钥库重置">点击下一步" >点击上传密钥重置请求" >点击与Google Play开发者支持联系"； >然后选择一种联系方式与他们联系以为您重置.

In the play console click the help button at the top > Scroll down to heed more help and click "Contact Us" > Type in you need help with a Keystore Reset > Click "next step" > Click "Upload key reset request" > Click "Contact Google Play Developer Support" > Then choose a contact method to contact them to reset it for you.

这篇关于我如何解决后续的.apk上传证书与原始证书不同的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！