When updating APK, Google Play tells the APK is not signed, but it is.

Hi.
When uploading a new updated APK for my AIR app, Google Play tells the APK is not signed.
I signed the APK with the same p12 file I used for the first version (successfully published and approved on Google Play).
I'm using Flash Builder 4.6 with AIR SDK 3.7. The first version of app was packaged with Flash Builder 4.6 and AIR SDK 3.4.
Then I tried to generate a new .p12 key, but I get the same error message while uploading.

Hi there, I agree with poltergeist_ and and thanks for the post mentioning that error message, even though this original topic was not related, so that I found this topic!
I updated my apps on Apr 16 using whatever the latest Air SDK that day (3.7.x I believe), and for some reason until now those updated apps works/install from Google play on all the existing android devices I had.
Yesterday I bought new Galaxy s4 and when I try to intall the updated apps, it is not installing on it saying "Package file was not signed correctly", so I spent bunch of time trying to figure out if this was because of this new Galaxy S4 phone. I'm glad that I found this topic and this post.
I'm gonna try it with new SDK build and will let you know the results.

Similar Messages

Maybe you are looking for