简体   繁体   English

android - 必须使用与先前版本相同的证书对apk进行签名

[英]android - the apk must be signed with the same certificates as the previous version

I am trying to upload my Android app to the Google Play market and I get the error: 我正在尝试将我的Android应用上传到Google Play市场并收到错误消息:

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

The funny thing is I am using the original keystone with the original passwords, so I am confused as to what could be causing this problem. 有趣的是我使用原始密钥和原始密码,所以我对可能导致此问题的原因感到困惑。

1) I did upgrade my Mac OS X to Lion which a 64 bit OS from I think the earlier 32 bit OS. 1)我确实将我的Mac OS X升级到了Lion,而我认为早期的32位操作系统是64位操作系统。 Could that be the problem? 这可能是问题吗?

2) I did update the Android tools: Eclipse, SDK and Java before making this new app version. 2)在制作这个新的应用程序版本之前,我确实更新了Android工具:Eclipse,SDK和Java。 Could that be the problem? 这可能是问题吗?

3) I also tried running 3)我也试过跑步

jarsigner -verify -verbose -certs

on the old version of the app that is on Google Play and the new app and the certificate valid times are the same. 在Google Play上的旧版应用程序和新应用程序以及证书有效时间相同。

4) I created the new APK both manually and by using Export Android Application in Eclipse. 4)我手动创建了新的APK,并在Eclipse中使用Export Android Application。

5) Manually I created the APK by within Eclipse using ` 5)手动我在Eclipse中使用`创建了APK

Android Tools -> Export Unsigned Application and then using
jarsigner -verbose -keystore mykeystore.keystore app.apk companyName
/Developer/android-sdk-mac_86/tools/zipalign -v 4 app.apk app_aligned.apk

So I don't think the problem is that I am using the wrong keystore. 所以我认为问题不在于我使用的是错误的密钥库。 I've read that this problem could also be caused by 我读过这个问题也可能是由于

A) Trying to upload a debug apk instead of a release apk. A)尝试上传调试apk而不是发布apk。

B) Having the wrong package name in the manifest. B)清单中包含错误的包名称。

C) Not incrementing the versionCode and versionName. C)不增加versionCode和versionName。

Are there other things that could cause this problem besides using the wrong keystone? 除了使用错误的梯形校正之外还有其他可能导致此问题的事情吗?

Well in my case it turns out I was using the wrong keystore. 在我的情况下,事实证明我使用了错误的密钥库。 What lead me to realizing this was running 是什么导致我意识到这一点正在运行

jarsigner -verify -verbose -certs android_app

on the previous and new app and getting a different CERT.RSA filename for each. 在上一个和新的应用程序,并为每个应用程序获取不同的CERT.RSA文件名。

So I dug around a bit and found another keystore, which turned out to be the correct one. 所以我挖了一下,找到了另一个密钥库,结果证明是正确的。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 apk 必须使用与之前版本相同的证书进行签名 - The apk must be signed with the same certificates as the previous version apk必须使用与上一个相同的证书签名 - The apk must be signed with the same certificates as the previous one apk必须使用与先前相同的证书签名 - The apk must be signed with the same certificates as the previous 在市场上上传apk时,必须使用与先前版本相同的证书对apk进行签名 - The apk must be signed with the same certificates as the previous version while uploading apk on market Android apk上传失败,并显示错误消息“该apk必须使用与上一个相同的证书签名” - Android apk upload fails with error 'The apk must be signed with the same certificates as the previous one' apk必须使用与先前版本相同的证书签名[发布具有其他信息的应用程序] - The apk must be signed with the same certificates as the previous version [release app with other informations] apk必须使用相同的证书签名 - The apk must be signed with the same certificates Android 上传到市场时出错:apk 必须使用与前一个相同的证书进行签名 - Android error while upload to market: The apk must be signed with the same certificates as the previous one 错误必须使用相同的证书对apk进行签名 - Error The apk must be signed with the same certificates apk必须使用相同的证书签名,即使旧证书不正确 - The apk must be signed with the same certificates even if old one is not correct
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM