Megha Joshi wrote: [...] > Your ADT error might be due to the keytool issue related to locale...see > the link below: > http://code.google.com/android/kb/troubleshooting.html#signingcalendar
I'm UKian, and as far as we know we use the Gregorian calendar too...
Creating and building an empty project on the command line produces what
appears to be the same error:
debug:
[echo] Packaging bin/ActivityName-debug.apk, and signing it with a
debug key...
[exec] Current OS is Linux
[exec] Executing
'/home/dg/apps/android-sdk-linux_x86-0.9_beta/tools/apkbuilder' with
arguments:
[exec] '/tmp/myproject/bin/ActivityName-debug.apk'
[exec] '-z'
[exec] '/tmp/myproject/bin/ActivityName.ap_'
[exec] '-f'
[exec] '/tmp/myproject/bin/classes.dex'
[exec] '-rf'
[exec] '/tmp/myproject/src'
[exec] '-rj'
[exec] '/tmp/myproject/libs'
[exec]
[exec] The ' characters around the executable and arguments are
[exec] not part of the command.
[exec] null
And, indeed, running apkbuilder directly from the command line just
produces:
null
> Also, someone else on the group..was able to resolve a similar Generic
> ADT error by switching back to JDK 5 from JDK 6.
Both java-1.5.0-sun and java-6-sun fail in precisely the same way.
...
UPDATE: I just tried deleting the debug.keystore file and rerunning
apkbuilder, to see if any interesting messages came out... and
everything works now. So obviously some of my fiddling managed to fix
something, but I don't know what; I'd already *done* that.
So while this appears to be all fixed now, I don't know why --- so I'm
going to go ahead and post this message in case anyone else has the same
problem and can clarify.
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ "All power corrupts, but we need electricity." --- Diana Wynne Jones,
│ _Archer's Goon_
signature.asc
Description: OpenPGP digital signature
