The Keystore Manager is a window which allows you to create, configure or load Android keystoresAn Android system that lets you store cryptographic key entries for enhanced device security. More info
See in Glossary and keys. For further information see Android’s Keys, Certificates and Keystores documentation.
To open the Keystore Manager, open the Android publishing window and select the Keystore Manager button.
Property | Description |
---|---|
Keystore dropdown | Use the Keystore dropdown to create a new keystore or select an existing one. Select Create New to create a new keystore. Select Anywhere to save the keystore file in your Project folder, or In Dedicated Location to create and save it to a different directory. Select Select Existing > Browse to select a keystore you already have. See Choosing your keystore location for more details. |
Password | Enter your keystore password. If you are creating a new keystore, use this field to create a password. |
Confirm Password (only required when you create a new keystore) | Use this to confirm the password for your new keystore. |
Existing keys | The Keystore Manager window automatically populates the Existing Keys field when you load an existing keystore into your project. |
New Key Values | If you have created a new key, you need to complete these fields. If you have loaded existing keys, you do not need to complete these fields. The New Key Values fields request the same information that Android Studio requests when you generate a key or keystore. This information is not displayed in your app, but is included in your certificate as part of the Android Package (APK). For further information, see Android’s Generate an upload key and keystore documentation. Unity does not validate this information. If you leave these fields blank, Unity uses empty values. This might affect the validity of your key. |
Alias | Enter an identifying name for your key. |
Password | Choose and enter a password for your key. |
Confirm password | Enter the password for your key again. |
Validity (years) | Enter an amount of time (in years) that your key is valid for. This should exceed the amount of time you expect to manage your application for, so that you can use the same key to sign application updates. The default validity is 25 years. |
First and Last Name | Enter your first and last name. |
Organizational Unit | Enter your organizational unit. Organizational units are the different divisions within an organization. For example: Android development team. |
Organization | Enter the organization that manages your application. For example: your company name. |
City or Locality | Enter your city or locality. |
State or Province | Enter your state or province. |
Country Code | Enter your country code. |
Note: You cannot change this keystore, key or certificate information once you sign your Android app.
Use the Keystore dropdown to create a new keystore.
Creating a new keystore automatically creates a new key. Fill in the New Key fields in the keystore manager.
When you create a new keystore, the storage location you choose changes the default location that Unity opens your file explorer in to save your file. You can still change this after the file explorer opens.
- Choose Anywhere to open the file explorer. By default, Unity stores your keystore inside your project folder. However, you can store this anywhere on your machine. If you store your keystore outside of your project folder, Unity saves an absolute path.
- Choose In Dedicated Location to open the file explorer in a custom default location. By default, this path points to $HOME/
on MacOS and to %USER_HOME%\
on Windows.
To define a new project-wide dedicated location, go to Unity > Preferences > External Tools > Android > Keystores Dedicated Location, then click Browse to select a location or enter a path in the text box.
If you store a keystore to a dedicated location, Unity saves a relative path. This relative path is equal to the dedicated location paths on other machines. Therefore, the folders don’t need to be in the same place on both machines.
Note that if you save the new keystore outside of your project folder or a shared directory, collaborators on your project might not have access to it.
Use the Keystore dropdown to load an existing keystore.
If you have multiple keys in your keystore, select a key for your project in the Android Publishing Settings Project Key fields.
Note: You can also choose an existing keystore directly from the Android Publishing Settings, without using the Keystore Manager window.
Use the following steps to store multiple keys in a keystore.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising. Some 3rd party video providers do not allow video views without targeting cookies. If you are experiencing difficulty viewing a video, you will need to set your cookie preferences for targeting to yes if you wish to view videos from these providers. Unity does not control this.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.