Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.4.X
Votes
0
Found in
2019.1.0a10
Issue ID
1167092
Regression
No
Android builds fail if building App Bundle with signed keystore/key that contains non-ASCII symbols in its name or password
How to reproduce:
1. Open attached "KeystoreTest" project
2. Go to File -> Build Settings -> Player Settings -> Publishing Settings
3. Type in (or copy+paste) the password for "newKeystore.keystore" - "À È Ì Ò Ù Ỳ Ǹ Ẁ" (without quotes)
4. Type in (or copy+paste) the same password for project key
5. Build the App Bundle
Expected result - Build is successful
Actual result - Builds fails with error message: "java.lang.RuntimeException: java.lang.RuntimeException: jarsigner.exefailed with exit code 1" (see full editor log below)
Reproducible with - 2019.3.0a9, 2019.2.0b9, 2019.1.9f1, 2019.1.0b1, 2018.3, 2018.2, 2018.1, 2017.4
Note - Building APK is successful and does not fail with the same setup
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
- Crash with ComputeTileMeshJob when generating Navmesh
Resolution Note (fix version 2020.1):
PR https://ono.unity3d.com/unity/unity/pull-request/91477/_/platform/android/aab_password_fix
Landed 2020.1.0a2