Sunday, May 29, 2011

Building signed packages

The Android system requires that all application be digitally signed as described here and here. During the development they can be signed with debug key that has known values and password so the developer does not need to be asked for details how to do this step.

You have to have your own private key and perform the build using this key before you publish your application though. So far the support for such a build was missing in nbandroid but this has changed. The latest snapshot adds a wizard hooked to an action available on project context menu to export signed application package. Values from project's properties files are used to assist you. Namely and key.alias are two basic properties to determine the location of keystore and name of the key used to sign the application. You can try it using the bits from continuous build and it will propagate to the stable update center in a few days if no bugs are reported.


  1. This looks like a great feature to have, but it doesn't work correctly currently.
    The "create new keystore option" does nothing (possibly does something near the end of the wizard) so the second step will not work (with any selection) as it reports that "The system cannot find the file specified" and the next button is greyed out.

  2. I filed a bug for you. Please, always use JIRA for something what is obviously a bug as described in Contacts page. It is fixed now and updated version is available through auto update.

  3. To be honest I didn't file a bug because I thought I may be doing something amazingly stupid. Just ran thru it and it works perfectly! You guys are fantastic!