The build.xml created by activitycreator.py did not include signing
targets when I ran it. The release target creates the ${out-unsigned-
package} apk which is named ${ant.project.name}-unsigned.apk when I
run it.
Be sure to read: http://code.google.com/android/devel/sign-publish.html
First create a key. One way is to do this: keytool -genkey -validity
10000 -keystore mykeystore -alias mykeystorealias
I usually copy the unsigned release file to ${ant.project-name}.apk
jarsigner -keystore mykeystore -verbose bin/${ant.project.name}.apk
mykeystorealias
and then verify it to make sure it worked
jarsigner -verify -verbose bin/${ant.project.name}.apk
There are probably ant tasks out there to automate the signing, but I
haven't used them yet.
On Nov 18, 5:53 pm, Cristian <[EMAIL PROTECTED]> wrote:
> I'm switching my app creation to Ant to make things more automated. I
> originally was only using Eclipse. The docs say that using the command
> "ant release" creates an unsigned Android package that I will have to
> sign. I ran "ant release" then tried to use jarsigner using my private
> key but I kept getting an error
>
> jarsigner: unable to sign jar: java.util.zip.ZipException: invalid
> entry compressed size
>
> The dug inside the Android package and found out it already had a
> cert.rsa file in the META-INF directory. I installed and ran the app
> without every having to manually sign it.
>
> Does ant automatically sign my apps? If so, where does it get the
> private key and how do change it?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
