Android code-signing requires that you have an Android Keystore. If you are building Lite apps, the EachScape Builder assigns a keystore automatically to your account. For Enterprise customers, you must produce These are generally created using a command line tool that is part of the Android developer SDK. We are happy to create this for you; supply the following items, as appropriate.
- The package name, which usually looks like "com.example.myapp". See the note below about releasing multiple apps. It is important that the domain is one that you have ownership of.
- Your company name. This is a required item.
- An optional organization name which could be the division within the company. This is an optional item.
- An optional organizational unit which is a third level. If you supply an organization name and want to specify a more detailed level of your organization, you may supply this item as well.
Once we have this information, we will generate a keystore. The keystore can either be used to sign one app or many apps, but the keystore's package name must be unique. We will provide you with the keystore and its associated password. You must retain this file for as long as you desire to replace any apps in the store that were signed with this keystore. If you lose the file or its password, there is no way to replace the app in the store.
If you have multiple apps, one keystore can be used to sign all of them. All we will need to know is the package name each app is to have assigned to it and the package name assigned to the keystore that should be used to sign the app itself. As you can imagine, if you only have one keystore to keep track of, there's less work to manage the association of keystores to apps and their individual passwords: there's just one choice when there's only one for all your apps.