Android Tutorial Signing your application before uploading to Google Play

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.

 

[Erel]

I will check this issue.

 

[Erel]

I've checked and it works fine. I created two keys and I was able to switch between those keys without any problem.

Can you post the exact steps that you are doing (with screenshots if possible)?

 

[chfajardo]

Still have problems to load a valid private sign key

Erel,

The steps i´m taking are simple:

1. If i create the private sign key right now and click ok, it works real fine.
2. If i try to load this same private sign key, i have the error message.
Note: I was able to sign my application using this batch file i wrote:

path = E:\Program Files\Java\jdk1.6.0_29\bin
jarsigner -verbose -keystore chave01.keystore -keypass xxxxxxxxxxx /bin/temp.ap_ b4a
path = E:\Program Files\Android\android-sdk\tools
zipalign -f -v 4 ./bin/temp.ap_ controlador_artnet_FULL_chfsoft.apk

So, it is clear that my private sign key is valid, and i even updated my android markey application.
Now the question is: Why i can not load my valid private sign key?
There are the steps i followed in the images attached.

-Image one: There is the screen when i click tools -> private sign key. If i click ok here, it works;

-Image two: Here, i have clicked the browse button and selected the same private sign key.

-Image three: Identical to image one, but in this one i have browsed and selected the private sign key. Now when i click the Ok button, i get this error.

 

[Erel]

This is strange. I removed the images (your password was shown there). Can you send me your file and password by mail to: erel@basic4ppc.com ?

 

[chfajardo]

Problems loading private sign key

Erel,

I will do better.
I am generating a new key using Basic4Android and will send to your e-mail.

 

[Erel]

Just make sure that you cannot reload it.

 

[chfajardo]

problem loading keystore file

Erel,

As i told you, none of my keystore files generated in Basic4Android is being loaded with success. I tryed this one too, and i have the same error.
The Load option is not working for me, and i don't know why.

 

[Erel]

The file you sent me works fine here.

When a keystore file is loaded, the keytool.exe -list command is issued to check that the password is correct. I do not know why it fails on your computer.
You can try putting the keystore file in a path without spaces and any special characters, though I doubt that it will help.

You can however edit the INI file while Basic4android is closed and manually set the SignKeyFile and SignKeyPassword values. This should work.
The ini file is located here:
C:\Users\<user>\AppData\Roaming\Anywhere Software\Basic4android\b4aV0.1.ini

 

[chfajardo]

Problems loading private sign key

Erel,

I will try this!
As soon i get it working i will tell you!

Best regards,

Carlos H. Fajardo.

 

[chfajardo]

Problems loading private sign key

Erel,

It works now, but it would be nice if i haven't to change the ini file every time.
It still shows me the same error when i click Ok Button.
Anyway, now i can compile my application and update it again on Android Market.
If it helps you, i'm using Windows 7 Home Premium and the installation is on drive E:

Please let me know if you get some fix for this issue.

Thanks!

Carlos H. Fajardo.

 

[cheese]

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

"The key is saved in this file" << which file? The one I am supposed to choose? I don't know what file to choose. Can I choose any file?

"You should choose the saving location" << Oh, so I am not supposed to select a file - I am supposed to choose a directory? Which directory?

 

[Erel]

When you create a new key, you are creating a new file. You should choose its name and location.

 

[pilbazan]

Always the same keystore file?

Hi,

I have a doubt. It is possible to use always the same 'keystore file' for all my applications? Or is better generate a new 'keystore file' for each new application? (always thinking in upload the application to the Market).

Thanks a lot

 

[NJDude]

One Keystore file is enough, however you can create more but keeping track of which app has which keystore might turn ugly.

 

[pilbazan]

Really thanks. I think I will use one keystore file.

 

[chfajardo]

keystore files

I strongly suggest you to use always the same keystore file, because even with Basioc4Android v.1.9 i still am not able to load keystore files. The only that works os the default one, if i do not try to load it.

 

[ssg]

This might give you a better idea on why you need to use multiple keystore:

Advice for Android Developers: Prepare for App Acquisition*|*metachris.org

Cheers!
-Bill

 

[Erel]

I don't think that it is a real issue. In the worst case you will need to give your private key to the company who acquired your app.

 

[moster67]

It also depends on if you are only licensing the app or if you are also selling the sources.

For a hired app I did, they paid me for the license to use the app in their name and while in this case it could have been sufficient to use only my own developer-key (since I would continue maintaining/improving the app myself), I still decided to create a specific developer-key for that app (and that company).

Important thing: keep the developer-key(s) in a safe place

 

[t0mt0m]

I put in my name, organization, country, and password, And when I hit ok i get this message saying Invalid file.

I am at registred User. Can you help me Please