So you can save on FedEx to Mountain View now ;) ? Anyways this is very helpful info for those (like me) who are not familiar with Android for Eclipse. jarsigner refuses to sign already signed apk (that is in-fact .jar file). What I did before was compiling in debug mode (with debug key) then manually erasing key info from the .apk and then signing it with jarsigner. It will save me lot of time, thanks nick
On Oct 28, 2:12 am, nick fox <[EMAIL PROTECTED]> wrote: > I have solved the problem. After going back and carefully re-reading > the publish and signing docs, I realized I had made a big mistake. > What I was doing wrong was I was using jarsigner on the .apk file that > was being automatically built by eclipse. This is incorrect. > > Here is the correct way to do it (as per the instructions in the > publish and signing docs). > > 1) right click on your project in the left package pane and select > Android Tools > Export Unsigned Application Package > 2) use jarsigner to sign the package you have just manually created > 3) use adb install to install the package on the phone (don't forget > to install the android usb drivers, only do this once) > > This tricky little error took me hours to figure out. I'm sure it's > going to mess up developers for years to come... That will teach me to > RTFM more carefully. > > Nick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
