0

When i try to uploading new update of my app, gives me this error "The apk must be signed with the same certificates as the previous version". Procedure: I use export wizard from eclipse, than load old cert file from my folder, i enter password correctly (i test it to enter incorrect, and cant go further) so i know for shure that is correct, and for alias the correct pass to, and save the apk. When i try to upload gives me the error. The package is the same, and oll the stuff. Can anyone tell me where is the problem ?

om3trix
  • 11
  • 3

2 Answers2

1

Most definitely your certificates are different, you may check using the following commands:

unzip -d tmp filename.apk META-INF/CERT.RSA
keytool -printcert -v -file tmp/META-INF/CERT.RSA

where filename.apk is you apk for current and/or previous version.

lenik
  • 23,228
  • 4
  • 34
  • 43
0

One of three things could cause this problem:

  1. Using a different private key cert (sounds like you don't think this is your problem)

  2. Not increasing the versionCode and versionName in android manifest

  3. Using a different package name

Hopefully it's not that you lost the cert! Good luck! Someone mentioned that it is possible to sign an old version of your app with multiple certs, and then continue to use the one you still have like this

Community
  • 1
  • 1
Jameo
  • 4,507
  • 8
  • 40
  • 66
  • @om3trix even for the first update you must have 2 certs, debug and release. – lenik Nov 11 '12 at 23:57
  • Sorry, i'm little confused "debug and release" ? If you are saying Keystore Selection and Key alias selection ? I entered correctly pass, because if you dont typed correctly you cant go to next step. I was trying to post some images here, but as a new user i can't :( – om3trix Nov 12 '12 at 00:15
  • By curiosity, i have 4 apps with 4 different certs, and with different passwords. Can that be a problem. Do i need to have one cert for all apps or not ? – om3trix Nov 12 '12 at 00:25
  • This is what the official docs say, but it seems like it should work with all different certs, just not recomended http://developer.android.com/tools/publishing/app-signing.html#strategies – Jameo Nov 12 '12 at 00:31
  • Honestly I really do feel like this has happened to me before though...try cleaning the project, quitting eclipse, re-open and try again – Jameo Nov 12 '12 at 00:32
  • I just tryed with my 2 other apps, SAME procedure and no problem at all. I think i have to quit in this one! – om3trix Nov 12 '12 at 01:18