HI,
getting this error The apk must be signed with the same certificates
as the previous version.
Please follow the steps
1. Made code changes to android app and changed the version from 1 to
2
2. Generated the signed application .apk from eclipse editor.
3. Tried to upload the apk file in the app store.
4. we have not used any certificate for the generating app in any
version.
5. Can u tell me why is this error coming?.
and how to fix this problem.
(2011/11/14 15:45), lakshman wrote: > HI, > getting this error The apk must be signed with the same certificates > as the previous version. > Please follow the steps > 1. Made code changes to android app and changed the version from 1 to > 2 > 2. Generated the signed application .apk from eclipse editor. > 3. Tried to upload the apk file in the app store. > 4. we have not used any certificate for the generating app in any > version. > 5. Can u tell me why is this error coming?. > and how to fix this problem.
> (2011/11/14 15:45), lakshman wrote:
> > HI,
> > getting this error The apk must be signed with the same certificates
> > as the previous version.
> > Please follow the steps
> > 1. Made code changes to android app and changed the version from 1 to
> > 2
> > 2. Generated the signed application .apk from eclipse editor.
> > 3. Tried to upload the apk file in the app store.
> > 4. we have not used any certificate for the generating app in any
> > version.
> > 5. Can u tell me why is this error coming?.
> > and how to fix this problem.
> > (2011/11/14 15:45), lakshman wrote:
> > > HI,
> > > getting this error The apk must be signed with the same certificates
> > > as the previous version.
> > > Please follow the steps
> > > 1. Made code changes to android app and changed the version from 1 to
> > > 2
> > > 2. Generated the signed application .apk from eclipse editor.
> > > 3. Tried to upload the apk file in the app store.
> > > 4. we have not used any certificate for the generating app in any
> > > version.
> > > 5. Can u tell me why is this error coming?.
> > > and how to fix this problem.
1) Export your app *unsigned* 2) Sign with your keystore using jarsigner (in your JRE directory) 3) Zipalign the apk
Then you'll be able to upgrade the app. Still, you have to do this every time you want to upgrade the app, since exporting it from Eclipse generates the same issue again.
It's all related to debug.keystore, in my opinion. Somehow the app is not signed correctly.
On Mon, Nov 28, 2011 at 12:13 AM, Mariux <mariu...@gmail.com> wrote: > It's all related to debug.keystore, in my opinion. Somehow the app is not > signed correctly.
Did you install Java 7? The jarsigner digest algorithm is different and produces a different signature.
I installed and configured Java 7 and the issue is unchanged.. How can I be sure it uses the correct Jarsigner? The jre configured in eclipse is jre7 but it compiles with Compiler 1.6 because Android can't be compiled in 1.7..
On Mon, Nov 28, 2011 at 8:23 AM, Mariux <mariu...@gmail.com> wrote: > I installed and configured Java 7 and the issue is unchanged.. How can I be > sure it uses the correct Jarsigner? The jre configured in eclipse is jre7 > but it compiles with Compiler 1.6 because Android can't be compiled in 1.7..
You don't have to install Java 7, but if you did you might get the 'signature different' issue. The correct jarsigner is the one from Java 6.
For what it's worth, I had a similar problem and it turned out I had upgraded Firefox. Someone mentioned I should use IE8 (I use winxp) and IE8 allowed the app to be updated thus correcting the problem. The next time I have to update/add an app to Android Market, I'll try Firefox just to see if it will work.
Best, Tom B
On Nov 14, 1:45 am, lakshman <laksh...@hyperwebenable.com> wrote:
> HI, > getting this error The apk must be signed with the same certificates > as the previous version. > Please follow the steps > 1. Made code changes to android app and changed the version from 1 to > 2 > 2. Generated the signed application .apk from eclipse editor. > 3. Tried to upload the apk file in the app store. > 4. we have not used any certificate for the generating app in any > version. > 5. Can u tell me why is this error coming?. > and how to fix this problem.
Tried with Chrome, Firefox and IE. Same issue for all of them.
In fact, this can't be a browser-related issue. If I manually sign the apk using jarsigner and then zipalign it, I'm able to upgrade the app. So probably it's something related to ADT mis-signing the apks!!
> Tried with Chrome, Firefox and IE. Same issue for all of them.
> In fact, this can't be a browser-related issue. If I manually sign the apk > using jarsigner and then zipalign it, I'm able to upgrade the app. So > probably it's something related to ADT mis-signing the apks!!
Issue seems fixed, I cleaned Eclipse with -clean, overwrote the keystore with a previous version and now the exported apk can upgrade in Developer Console!
I would suggest take the back up of the Android keystore that helps. Last time, when i was uploading it, accidental i deleted the keystores file, i had to change the package name again and generated the New keystore, It was a bad experience i had it.
On Mon, Nov 28, 2011 at 6:17 PM, Mariux <mariu...@gmail.com> wrote: > Issue seems fixed, I cleaned Eclipse with -clean, overwrote the keystore with a previous version and now the exported apk can upgrade in Developer Console!
> -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en
I made exactly the same mistake ! Customers that buy my newly released game have an "Package file was not signed correctly" error. I find that I signed my key with JAVA 1.7 keytool, that used as algorithm "SHA256withRSA" I was thinking this - default - algorithm is not supported by Android Publishing, and provoke this error.
So I rolled-back to JAVA 1.6, delete my key from my current keystore, and re-create one (same name) with "SHA1withDSA"
I thought that will solve my signature problem, but when uploading it in Google Play I encounter the message: "The apk must be signed with the same certificates as the previous version."
I'm really disapointed, the purpose of the new update was specifically to change my current certificate ! What can I do to release my application ?
PS: maybe someone know a command to change the algorithm with keytool without deleting/creating perhaps ?
On Wed, Oct 3, 2012 at 5:31 PM, Cyrille Paulhiac <cyr.paulh...@gmail.com> wrote:
> So I rolled-back to JAVA 1.6, delete my key from my current keystore, and
> re-create one (same name) with "SHA1withDSA"
> I thought that will solve my signature problem, but when uploading it in
> Google Play I encounter the message:
> "The apk must be signed with the same certificates as the previous version."
> I'm really disapointed, the purpose of the new update was specifically to
> change my current certificate !
> What can I do to release my application ?
I hope you have a backup of the original keystore. To change the signature
you only need to change the parameters you pass to jarsigner, not the
actual key. You are required to use the same key if you want to update
the application on the Google Play store.
Unfortunately not, because I was compiling my apk with Unity, and used an internal manager of keystore (and not knowing anything about jarsigner). So I unpublish my game and re-publish a new one, with a totaly new keystore and key. It works. I created a thread on Unity forums to alert them of JDK1.7 issue. Thanks again.
I hope you have a backup of the original keystore. To change the signature
> you only need to change the parameters you pass to jarsigner, not the > actual key. You are required to use the same key if you want to update > the application on the Google Play store.
