update app - update incompatibile, signatures do not match?!

Solar2D Android
#1

Hi,

I published some app in google play store, in last weeks did 3 updates, everything works fine…

Yesterday I did some bigger changes (changing orientation possible - turning off landscape - and many more)

…and today I see: 

ERROR: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.some.package signatures do not match the previously installed version; ignoring!] Error found during installation!

 

Why? 

#2

Did you build with the correct certificate?

#3

the same as always - I have build with debug cert, and i have enabled signing app in google play 

#4

Wow, that is not the way I would go.  What made you choose that instead of creating your own signing certificate?

I ask,

  1. I didn’t think the docs suggested that (but maybe I’m wrong?)

  2. I don’t trust the signing app in Google for this very reason.  I like full control of my binary.

Sorry you’re having troubles but this is an area I have no helpful experience with.

PS - Actually, I have to wonder if maybe you updated Corona recently and got an updated debug certificate?

PPS - There is also the distinct possibility that the ‘generated certificate’ from Google is based on some of those things you changed.  (although it should really only be based on the package ID)

Question: Is there any way to download the generated certificate from a prior build and to simply use it in your own build?

#5

Oh, and this may be a stupid question, but you used the same package ID as prior builds right?

#6

yes, used the same package id. And I don’t see option to download keys from google.

But guys, actually nevermind, google suspended my app. In policy questionnaire I tried to select that alcohol/drugs/body parts (of animated characters!) appears but it ranked it at 3+ years old. And now suspension. I’m not yet sure if it was because images there were not acceptable at all, or not acceptable for that ranking, anyone more experienced with their policy can take a look and advice? Should took no more than 2-4 minutes.

Now I’ll have to upload new app :( 

…so I’ll get a chance to take care of keys myself. :wink:

#7

I know some users have gotten the Google key management working, but it’s not something we recommend. Manage them yourself and create your own release keystore.

Rob

#8

Remember to store aside (someplace safe):

  • keystore file
  • Exact steps you used including details you filled into questionnaire and password(s) you used.
  • Cersion of JDK you used.

If you can’t remember your passwords , lose your keystore, or can’t reproduce it you’ll be hosed the next time you need to build and upload.

#9

Did you build with the correct certificate?

#10

the same as always - I have build with debug cert, and i have enabled signing app in google play 

#11

Wow, that is not the way I would go.  What made you choose that instead of creating your own signing certificate?

I ask,

  1. I didn’t think the docs suggested that (but maybe I’m wrong?)

  2. I don’t trust the signing app in Google for this very reason.  I like full control of my binary.

Sorry you’re having troubles but this is an area I have no helpful experience with.

PS - Actually, I have to wonder if maybe you updated Corona recently and got an updated debug certificate?

PPS - There is also the distinct possibility that the ‘generated certificate’ from Google is based on some of those things you changed.  (although it should really only be based on the package ID)

Question: Is there any way to download the generated certificate from a prior build and to simply use it in your own build?

#12

Oh, and this may be a stupid question, but you used the same package ID as prior builds right?

#13

yes, used the same package id. And I don’t see option to download keys from google.

But guys, actually nevermind, google suspended my app. In policy questionnaire I tried to select that alcohol/drugs/body parts (of animated characters!) appears but it ranked it at 3+ years old. And now suspension. I’m not yet sure if it was because images there were not acceptable at all, or not acceptable for that ranking, anyone more experienced with their policy can take a look and advice? Should took no more than 2-4 minutes.

Now I’ll have to upload new app :( 

…so I’ll get a chance to take care of keys myself. :wink:

#14

I know some users have gotten the Google key management working, but it’s not something we recommend. Manage them yourself and create your own release keystore.

Rob

#15

Remember to store aside (someplace safe):

  • keystore file
  • Exact steps you used including details you filled into questionnaire and password(s) you used.
  • Cersion of JDK you used.

If you can’t remember your passwords , lose your keystore, or can’t reproduce it you’ll be hosed the next time you need to build and upload.