Hello everybody
I was uploading 2 apps to the market .There was no "signing in "error ,the package name and so on was ok…
but if the user is trying to install the app the message:
“package was not signed correctly”
Found some info here in the forum but Im confused and right now Im trying to downgrade to jdk 1.6.
my app was already for 2 weeks in the market and I think i was using jdk1.7 without this problem.
Any suggestions about how to solve this.
I would be glad for some explanations to this unity-jdk problem.
Same problem … hours of test, no victory…
it’s very cruel.
Strangely, on rare devices on Android 2.2, download is possible !
A strange new thing, using the Google Play Old Interface, my APK is rejected, cause to a non “activated signature”, with the new interface, the APK is validated ! maybe, the problem is from Google Play interface ? but how to know! i mailed them, maybe one day the response will fall
Hello hello,
For information, i manage to avoid the “Package was not signed correctly” problem, after Google Play submission.
I don’t have a clear response on what was the matter, but there is the tips i used :
- Compiled on JDK 1.6 instead of JDK 1.7
- verify all Environment variable, (be sure to restart Windows too…), test it with “path” in command lines
- Use of old Google Play interface instead of New (more alerts if Apk is invalid)
- reinstall Unity licence keys
- use last version of Unity 3-56 instead of 3_53
- regen Android XML Manifest files
I hope it could help people in distress !
Have Fun in Unity Milky way
Hi, I tryed to follow your way but if I create another key (with java 1.6), when a I upload to the old google play console interface I receive the error:" sign with the preview key". How can I re-compile the same key with java 1.6 ? The same name is enought ?