Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.1.0a1
2018.1.0a3
Issue ID
976618
Regression
Yes
Signing Keystore for Android fails when using non-english characters on Windows
Steps to reproduce:
1. Open attached project
2. File -> Build Settings -> Publishing Settings
3. Check "Create a new keystore..."
4. Put "helloこんにちは" or any other combination of english and non-english characters into "Keystore password" and "Confirm keystore password" fields
5. In Key section press on Alias drop-down and select "Create a new key"
6. "Create a new key" window will popup, fill first 3 fields with the same password you created earlier and press "Create key"
7. In the Key section type the password again and start building for Android
-Key signing will fail and build process will stop
Expected result: Key signing should support other languages as keys
Reproduced on: 2017.1.0a1, 2017.1.0a2, 2017.1.0b9, 2017.1.2p2, 2017.2.1f1, 2018.1.0.a3
Regression found in 2017.1.0a1
Does not reproduce on: 5.6.3p3, 5.6.3p4
Note: Only reproduces on Windows
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Tile Palette grid is moved after entering Play Mode
- Tile Palette Edit mode turns off in Play Mode
- The Editor crashes when Generating Font Atlas in the Font Asset Creator with “9999999999” padding and 256x256 Atlas Resolution
- [iOS] An “ArgumentNullException” error is thrown when GetIntroductoryPriceDictionary() method is called
- Font Import Settings documentation page is missing when the documentation button is pressed in the Inspector window
Add comment