Search Issue Tracker

Fixed in 2019.2

Votes

3

Found in

2017.2.0p2

Issue ID

977673

Regression

Yes

Android Keystore location saved as absolute value in Project Settings

Mobile

-

Steps to reproduce:
1. Open new project
2. In Player settings for Android, under Publishing settings, open the Keystore Manager window
3. Click the Keystore... Dropdown and select "Create new -> Anywhere"
4. Save the keystore in the project directory under any name
5. Input password and Alias with its password to create a new key
6. Click Add key, and when prompted whether to use this Keystore and Alias for your project, click Yes
7. Observe the Path to the keystore showing as "{name}.keystore"
8. Open the Keystore Manager again and Create a new alias in the same keystore
9. Click Add key, and when prompted whether to use this Keystore and Alias for your project, click Yes
10. Observe the Path to the keystore showing as "{full_path_to_keystore}\{name}.keystore"
11. Now when copied to a new directory, the project will try to use the old keystore, rather than the relative new one in the copied project

Expected: After creating the second alias in step 8 and 9, the path to the keystore should still be the relative path as we saw in step 7
Actual: After the second alias is created, the path becomes absolute and will use the same keystore path no matter where the project is located

Reproduced on: 2019.1.0a12 (Keystore manager introduced), 2019.1.1f1, 2019.2.0a14, 2019.3.0a2

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.