Signing your application before uploading to Android market

[Erel]

The result of compiling your application is an APK file. This is a package file that contains the compiled source code and the assets files.
The APK file must be signed before installation. Signing the file means that it is not possible to later modify it without the private key that was used to sign the file.
Android devices will not install an unsigned APK file.

Basic4android uses a default "debug key" to sign applications. This key is fine during debugging. However Android market doesn't accept APK files signed with this key.
You need to create your own private key.
Fortunately it is pretty simple to create such key.
Choose Tools - Private Sign Key



This dialog allows you to create a new key, load an existing one or to use the debug key.
Keys are stored in a keystore file.
It is not possible to access such a file without its password.

Once you created a new keystore file, Basic4android will use this key for all your projects.
You should be very careful with this file. If this file gets lost you will not be able to update your applications in the market. You will need to publish updates as new applications.
It is impossible to recreate a lost keystore file.
Therefore it is recommended to backup this file.

In the IDE, when you reinstall an application and use a different key, you will see this message:


Pressing yes will uninstall the previous application and install the new one.

[GeoTrail]

I tried compiling a small app to test.
It worked great on the emulator, but when I ran it on my phone, it just displayed a black screen with the title I added.

And when I tried uploading it to the Market Place, I got errors like, missing icons and stuff. Can't remember them all now, I'm at work and can't install it here.

[Erel]

You will need to add some more information. It will be better to open a new thread for this here: Basic4android Updates and Questions - Basic4ppc / Basic4android - Android programming

[GeoTrail]

Yeah I figured that. But I'm not sure exactly what to fill in, or how to add the icon. The manifest isn't supposed to be uploaded?

Sorry about posting in the wrong place.
You just reminded me of the problem I had when I read your post here.

[Erel]

The manifest is included in the APK file. There is a field in the market upload form for uploading an image as an icon.

[mistermentality]

Excuse me for asking a silly question but with a previous version of B4A I had to manually sign my apk files with my key if not using one generated by b4A.

I tried with the new version (1.6) loading my keystore in and this time get no warnings during compile, does this mean it has changed and can now use a non b4a generated key?

Dave

[Erel]

I tried with the new version (1.6) loading my keystore in and this time get no warnings during compile, does this mean it has changed and can now use a non b4a generated key?

No. Nothing has changed in v1.6 related to signing keys.

[demasi]

Please help: what is this file to be filled in the "private sign key" dialog? (first message) where can I find it?

[Erel]

The key is saved in this file. You should choose the saving location.

[rafaelbrasilia]

Hi,
I'm truing to create a new keystore file but I keep getting this Invalid file message.

I put in my name, organization, country, and password, And when I hit ok i get this message saying Invalid file.
Should i chose a file in the file field, even though I want to create a new keystore file?

thanks!
rafael