Quantcast
Channel: Appcelerator Developer Center Q&A Unanswered Questions 20
Viewing all articles
Browse latest Browse all 8068

Issue with Keystore generated by JDK 1.7 and app signed by 1.6

$
0
0

So I just finished an app for a client and was getting ready to push to Google Play store. The client sent over a keystore that he generated (using JDK 1.7). I then built it against JDK 1.6 and no errors, uploaded to play store and now I am getting the dreaded 'Package file was not signed correctly'.

So I decided I would just create a new keystore using JDK 1.6 on my machine. The problem is I already uploaded the app on the Play Store so I can not use this new keystore with that app on Google Play.

So to me it sounds like there are only 2 options, please correct me if I am wrong.

  1. Somehow build the app with JDK 1.7, even though in the Titanium compatibility matrix it says only 1.6 is supported.

  2. Remove my app from the store, change the reverse domain name slightly, and then republish the app with JDK 1.6 keystore and build.

Anyone ever have this issue or recommend one or the other? Any other alternatives?


Viewing all articles
Browse latest Browse all 8068

Trending Articles