blocks|key|3207380|text|没什么。阅读文档：Publishing+Updates+on+Android+Market|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3207381|3207382|在上传更新后的应用程序之前，请确保在清单文件的元素中增加了android:versionCode和android:versionName属性。此外，包名必须相同，并且.apk必须使用相同的私钥进行签名。如果包名称和签名证书与现有版本的不匹配，市场将认为它是一个新的应用程序，不会将其作为更新提供给用户。|blockquote|3207383|3207384|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/guide/publishing/publishing.html#marketupgrade^0|9|10|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|V|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Nothing. Read the documentation: <a href="http://developer.android.com/guide/publishing/publishing.html#marketupgrade">Publishing Updates on Android Market</a>

<blockquote>
 Before uploading the updated application, be sure that you have incremented the android:versionCode and android:versionName attributes in the element of the manifest file. Also, the package name must be the same and the .apk must be signed with the same private key. If the package name and signing certificate do not match those of the existing version, Market will consider it a new application and will not offer it to users as an update.
</blockquote>

blocks|key|3207403|text|什么都没有-谷歌明确表示，应用程序是由用于签名的密钥识别的。因此，如果您丢失了密钥，则需要创建一个新的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3207404|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Nothing - Google says it clearly that the application is identified by the keys used to sign it. Consequently if you've lost the keys, you need to create a new application.

blocks|key|2993992|text|我只是突然发现了这件事。我真的不认为我改变了什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2993993|但是，Build+=>+Clean+Project修复了它。|offset|length|style|CODE|2993994|entityMap^0|0|3|M|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I just had this occur out of the clear blue. I really do not think I changed anything.

However, <code>Build =&gt; Clean Project</code> fixed it.

blocks|key|2993959|text|今天我遇到了同样的问题，不幸的是，我的keystore文件中有两个别名。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2993960|📷|atomic|offset|length|2993961|​|2993962|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/a25d9ba8e445e89f37bfb511fcb9e35d.jpeg|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

Today i faced same issue, unfortunately, i was having two aliases in my keystore file.<a href="https://i.stack.imgur.com/CFdLl.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/CFdLl.jpg" alt="enter image description here"></a>

blocks|key|282221|text|这里我得到了这个问题的答案。在搜索了太长时间后，我终于破解了这个的密钥和密码。我忘记了我的密钥和别名，也忘记了jks文件，但幸运的是，我知道我放在里面的那堆密码。但是找到正确的组合对我来说是最困难的任务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|282222|解决方案-下载此插件-+Keytool+IUI版本2.4.1插件|282223|📷|atomic|offset|length|282224|此时将弹出窗口，显示您的jks文件的别名..if是否正确。右键单击别名并点击“查看证书链"..它将显示SHA1密钥。将此密钥与您在google应用商店中上传apk时获得的密钥进行匹配...|282225|如果它匹配，那么您使用的是正确的jks文件和别名。|282226|现在幸运的是我有一堆密码可以匹配..|282227|282228|​|282229|现在转到这个scrren，放入相同的jks路径..和password+(在您拥有的密码中)将任意路径放入"Certificate+file“中|282230|如果屏幕显示任何错误，则说明密码不匹配。如果它没有显示任何错误，则意味着您使用的是正确的jks文件。更正别名和密码()，这样你就可以在play商店上传你的apk了:)|282231|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/913ef5241ffb9c43e8f8f8a2f92279c2.jpeg|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/fde26b87a7abf33e35209ccbd3088737.jpeg^0|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@$G|19|H|1A|1|1B]]|A|$]]|$1|I|3|J|5|6|7|1C|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1D|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1E|8|@]|9|@]|A|$]]|$1|O|3|E|5|F|7|1F|8|@]|9|@$G|1G|H|1H|1|1I]]|A|$]]|$1|P|3|Q|5|6|7|1J|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1K|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1L|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12|13|-4]]|14|$5|Y|Z|10|A|$11|15|13|-4]]]]

Here i get the answer for that question . After searching for too long finally i get to crack the key and password for this . I forget my key and alias also the jks file but fortunately i know the bunch of password what i had put in it . but finding correct combinations for that was toughest task for me . 

Solution - 
 Download this - Keytool IUI version 2.4.1 plugin
<a href="https://i.stack.imgur.com/3lsq7.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/3lsq7.jpg" alt="enter image description here"></a> 

the window will pop up now it show the alias name ..if you jks file is correct .. 
right click on alias and hit "view certificates chain "..
it will show the SHA1 Key .. match this key with tha key you get while you was uploading the apk in google app store ... 

if it match then you are with the right jks file and alias .. 

now lucky i have bunch of password to match .. 
<a href="https://i.stack.imgur.com/llqVF.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/llqVF.jpg" alt="enter image description here"></a>

now go to this scrren put the same jks path .. and password(among the password you have ) put any path in "Certificate file"

if the screen shows any error then password is not matching .. if it doesn't show any error then it means you are with correct jks file . correct alias and password() 
now with that you can upload your apk in play store :)

blocks|key|283777|text|我强烈推荐Keystore+Explorer+(https://keystore-explorer.org/)，它可以让你访问你的密钥库，而不必上传到Google+Play。这样，您就可以排除输入密码是否错误的故障。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|283778|entityMap|0|LINK|mutability|MUTABLE|url|https://keystore-explorer.org/^0|O|U|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I highly recommend Keystore Explorer (<a href="https://keystore-explorer.org/" rel="nofollow noreferrer">https://keystore-explorer.org/</a>) which lets you access your keystore without having to upload it to Google Play. This way you can troubleshoot whether you are entering your password incorrectly.

blocks|key|282206|text|如果你有以前apk文件(备份)，然后使用jarSigner从该apk提取证书，然后使用密钥或使用密钥工具克隆该证书，这可能会有所帮助…有用的链接是jarsigner+docs和keytool+docs。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|282207|entityMap|0|LINK|mutability|MUTABLE|url|http://download.oracle.com/javase/1.3/docs/tooldocs/win32/jarsigner.html|1|http://download.oracle.com/javase/1.3/docs/tooldocs/win32/keytool.html^0|21|E|0|2G|C|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

If you have previous apk file with you(backup) then use jarSigner to extract certificate from that that apk, then use that key or use keytool to clone that certificate, may be that will help...
Helpful links are <a href="http://download.oracle.com/javase/1.3/docs/tooldocs/win32/jarsigner.html" rel="nofollow noreferrer">jarsigner docs</a> and <a href="http://download.oracle.com/javase/1.3/docs/tooldocs/win32/keytool.html" rel="nofollow noreferrer">keytool docs</a>.

blocks|key|2993975|text|我最近遇到了这个问题，在尝试了不同的登录方式后，比如启用V1或V2，通过更改别名和登录，最后才知道我使用的是错误的密钥存储文件|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2993976|entityMap^0|15|M|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I had faced this issue recently, after trying different ways to sign in like enable V1 Or V2, signed in by changing alias name and last come to know that I am using wrong key store file

blocks|key|3207543|text|您可以使用新功能Google+play应用程序签名来生成新的密钥文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3207544|2017年5月之后，Google+play商店在Play商店上添加了一个新功能，这对Android开发人员来说是个好消息。通过此功能，开发人员可以更新丢失KeyStore文件的应用程序或应用程序密钥。你需要在play+store主机上启用google+play应用程序签名。|3207545|https://support.google.com/googleplay/android-developer/answer/7384423?hl=en|offset|length|3207546|http://www.geekcodehub.com/2018/05/23/keystore-lost-in-android/|3207547|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|24|0|0|0|1R|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$F|Y|G|Z|1|10]]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|E]]|Q|$5|M|N|O|A|$P|I]]]]

You can use new feature Google play app signing to generate a new key file .

After May 2017 Google play store add a new feature on Play store and
It’s Good News For Android Developers.
From this feature, Developer can update their app or Apk who lost a KeyStore file.
you need to enable google play app signing on play store console.

<a href="https://support.google.com/googleplay/android-developer/answer/7384423?hl=en" rel="nofollow noreferrer">https://support.google.com/googleplay/android-developer/answer/7384423?hl=en</a>

<a href="http://www.geekcodehub.com/2018/05/23/keystore-lost-in-android/" rel="nofollow noreferrer">http://www.geekcodehub.com/2018/05/23/keystore-lost-in-android/</a>

blocks|key|280186|text|我愚蠢的错误是我使用了app-debug.apk文件而不是app-release.apk+ase.apk文件。您需要在生成签名APK时，在“构建变体”框中选择"release“。app-release+ase.apk文件应该位于项目根目录下的"app\release“文件夹下。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|280187|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My [silly] mistake was that i used app-debug.apk file instead of app-release.apk file.
You need to to choose "release" in "Build Variants" frame when you generate signed APK.
The app-release.apk file should be located under "app\release" folder in your project root.

I had uploaded my app to Google Play (back when it was called Android Market) some time ago.

Today I updated the app, but I had deleted the previous keystore and created a new one. 
When uploading, it says the APK must be signed with the same certificates as the previous version:

<blockquote>
 Upload failed
 
 You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate.
 
 Your existing APKs are signed with the certificate(s) with fingerprint(s): 
 [ SHA1: 89:2F:11:FE:CE:D6:CC:DF:65:E7:76:3E:DD:A7:96:4F:84:DD:BA:33 ] 
 and the certificate(s) used to sign the APK you uploaded have fingerprint(s): 
 [ SHA1: 20:26:F4:C1:DF:0F:2B:D9:46:03:FF:AB:07:B1:28:7B:9C:75:44:CC ]
</blockquote>

But I don't have this certificate, and don't want to delete and re-publish the application, because it has active users.

What can I do to sign my app with new certificate?

The apk must be signed with the same certificates as the previous version

不久前，我把我的应用程序上传到了Google Play (当时它被称为Android Market)。今天我更新了应用程序，但我已经删除了以前的keystore，并创建了一个新的。上传时，它要求APK必须使用与前一个版本相同的证书签名：上传失败您上载的APK使用与以前的APK不同的证书签名。您必须使用相同的证书。您现有的APK使用带有指纹的证书进行签名：89:2F:11:FE:CE:D6:CC:D

问apk必须使用与上一版本相同的证书进行签名
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问apk必须使用与上一版本相同的证书进行签名EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问apk必须使用与上一版本相同的证书进行签名
EN