WARNING: Signing for release with Java 7 broken!
13 views
Skip to first unread message
donV
Dec 28, 2011, 8:11:39 PM12/28/11
to Ruboto (JRuby on Android)
I just spent an hour trying to publish a new version of the Ruboto
Startup Timer. The apks were accepted by the Android Market, but when
they reached the device, they were rejected with "The package was not
signed correctly"
I do not have the details of the cause, but the "fix" was to revert
from OpenJDK 7 to Apple Java 6. I found a couple of links about this,
so the problem is known, but not fixed.
Be warned that using OpenJDK to sign apps for release may cause
trouble when the apk reaches the device.
Startup Timer. The apks were accepted by the Android Market, but when
they reached the device, they were rejected with "The package was not
signed correctly"
I do not have the details of the cause, but the "fix" was to revert
from OpenJDK 7 to Apple Java 6. I found a couple of links about this,
so the problem is known, but not fixed.
Be warned that using OpenJDK to sign apps for release may cause
trouble when the apk reaches the device.
Reply all
Reply to author
Forward
0 new messages