2

I created an Android app and published it within the Google Play Store. Upon subsequent download, I receive the “Package file was not signed correctly” error. I investigated and found the entry:

Published Android apk gives error "Package file was not signed correctly"

I tried the JDK 6 solution (compile and sign under JDK 6) but there was no joy. I tried to download/install on both a 2.3.3 and 4.x device but neither would work. In my case, the app was new so the keystore is also (not an update) new. I will say that the new keystore was initially created under JDK 1.7.

I am stumped on how to approach resolving this issue, anyone have thoughts?

Community
  • 1
  • 1
Perry Hoekstra
  • 202
  • 2
  • 9
  • possible duplicate of [Published Android apk gives error "Package file was not signed correctly"](http://stackoverflow.com/questions/2519374/published-android-apk-gives-error-package-file-was-not-signed-correctly) – Jim G. Apr 26 '14 at 22:17

1 Answers1

0

I think I had this issue in the past. If you're using different folders for your layouts (for different screen size and different languages), can you check that the default folder for each resource is present ? (basically you need to have a folder res/drawable, res/layout, res/values etc... even if they're empty)

ben
  • 1,151
  • 10
  • 20
  • Yes, they exist. In addition, one of the apps is brand new (never been deployed to the App Store before) so it has no history. The common thread across all three is the error message. – Perry Hoekstra Jan 01 '13 at 15:26
  • The only major difference was the addition of ActionBarSherlock as a library. – Perry Hoekstra Jan 01 '13 at 21:47