Hey,
With the Eclipse plugin, it's all very easy. If you still have any
problems, I can help you..
On Sep 13, 6:57 am, Ken H hunt1...@gmail.com wrote:
I think I got it figured. I just have to do it the way the dev guide
says do it -- create a key in the keystore and apply that to the
I think your keystore location should not be your path to the .apk..
It should be
on another directory so you can access it anytime.
On Sep 13, 8:05 am, Ken H hunt1...@gmail.com wrote:
Thank you. That part is starting to sink in after reading it 10
times :)
My next problem/question is this:
Try to replace your keystore path. it should not be on your .apk
location.
On Sep 13, 8:05 am, Ken H hunt1...@gmail.com wrote:
Thank you. That part is starting to sink in after reading it 10
times :)
My next problem/question is this: when I fix some bugs in the app do I
need to re-sign it?
Your app needs to be digitally signed.
If you use Eclipse with the ADT plugin, skip to the Compiling and
signing with Eclipse ADT section. Otherwise, follow the instructions
to export an unsigned .apk and then sign it with jarsigner.
--
Jack Ha
Open Source Development Center
·T· · ·Mobile·
Thank you. That part is starting to sink in after reading it 10
times :)
My next problem/question is this: when I fix some bugs in the app do I
need to re-sign it? I just assumed I did, but when I do Export Signed
Application Package, give it the password for the keystore (the
keystore location
I think I got it figured. I just have to do it the way the dev guide
says do it -- create a key in the keystore and apply that to the
application. I'm new to the whole signing thing and using the Export
Signed Application Package confused me because there is no keystore
created (at least not one
6 matches
Mail list logo