Use the Keystore Manager window to create a new keystore to sign your application before publishing.
To create a new keystore:
Open the Keystore Manager window (menu: Edit > Project Settings > Player > Android > Publishing Settings).
In the top-left of the window, select Keystore > Create New.
Choose from the following options to save your keystore file to a default location. You can navigate to a different folder to save the file at any other location.
For more information, refer to Choose the keystore location.
In the Password field, enter a password for the keystore, then re-enter it in the Confirm password field.
Add a key to finish creating the keystore. For instructions, refer to Add keys to a keystore.
Note: A keystore must contain at least one key.
You can create a new keystore anywhere on your computer through the following options under Keystore > Create New. These options open a specific folder on your machine by default, which you can change.
| Option | Description |
|---|---|
| Anywhere | Opens the file explorer at the root of your Project folder. |
| In Dedicated Location | Opens the file explorer at the location set in Keystores Dedicated Location. By default, this path points to the home directory on your machine, $HOME/ on macOS and %USER_HOME%\ on Windows. To change this default path, go to Edit > Preferences (macOS: Unity > Settings) and then navigate to External Tools > Android > Keystores Dedicated Location. Select Browse to choose a location or enter a path in the text box. |
The keystore location determines how Unity stores the path to the keystore file. If you save the keystore in your Project folder or the dedicated location, Unity saves a relative path to the keystore. Otherwise Unity saves an absolute path to the keystore.
If you store a keystore in a dedicated location, each collaborator on your project can specify a different dedicated location on their machine to store the keystore file. Unity then resolves the keystore location using the dedicated location and the relative path. However, as the dedicated location is outside the Project folder, the keystore file isn’t tracked by version controlA system for managing file changes. You can use Unity in conjunction with most common version control tools, including Perforce, Git, Mercurial and Unity Version Control (UVCS). More info
See in Glossary, and hence not accessible for collaboration. To allow collaborators to access the same keystore file, consider storing the keystore file in a shared directory.