Signing application

by Tane Nguyen » Mon, 16 Nov 2009 12:48:53 GMT

Sponsored Links
 Hi everybody,

I'm very newbie in Android and right now I want to publish my
HelloWorld application that I made with Eclipse (Just to know that I
can export it, not literally sending it to public). I followed and
made the code that was in the website: 
and tested through the emulator and everything worked but signing out
(publishing) is giving me headache. I have tryied to make Basic Setup
for Signing and I think its ok but can anyone describe more specfic
about that path how its literally written. Is it c:\Program Files
(x86)\Java\jdk1.6.0_16\ or C:\Program Files (x86)\Java\jdk1.6.0_16\bin
\; or C:\Program Files (x86)\Java\jdk1.6.0_16\bin\keytool.exe; or C:
\Program Files (x86)\Java\jdk1.6.0_16\bin\jarsigner.exe;. And which
one is more better: JAVA_HOME or PATH

And by the way, I still can exprot it through the export wizard and it
gives me .apk-package but when I put it into my android device and
installing it, it gives installation was unsuccessfully or something
like that to remind that installation didn't success. Is it something
wrong when I made new keystore or something like that.

Thank you very much and I would appriciate if you are able to help me.

Tane Nguyen


Other Threads

1. SQLiteException thrown during rawQuery()


I got an SQLiteException when executing a rawQuery() function. I
checked the API on this, and noticed that it is not documented that
rawQuery would throw this (otherwise I would have put try/catch for
this). Is this just something that was missed or is there something
else in the documentation I need to be reading in regards handling to
handling SQLite syntax errors?

Thank you,

Steven Gillan


2. Why would SQLiteOpenHelper.onUpgrade fail?


every time i increase my database version and push the upgraded app to
the users, something weird happens.. For some it works perfectly fine,
and some report crashes (including through the Market's reporting
system) caused by the lack of table columns i just added in onUpgrade.
If you want to see the method:

I can't spot any exceptions that appear in onUpgrade. What i'm
currently doing to bypass these problems is intercepting the
exceptions where the new fields are invoked for the first time and
then calling onUpgrade 'manually', which is kind of dirty. Does anyone
have any idea what might be happening?



3. inner classes in android

4. How to synch SQL Lite database up with Database server

5. stripped down linux

6. developing a driver on beagle board

7. Loading music files into the emu android