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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
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