Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.2.0a1
2019.2.0a10
Issue ID
1141839
Regression
Yes
Keystore path is not interpreted correctly when Keystore is created in folder which has specific symbols in it's name string
Symbols include space ( ), coma (,), full stop (.), semicolon (;) and most likely any other characters, that are allowed in name string but require escaping when getting the path.
To reproduce:
1. Open any project, that has one of the symbols above in it's name, switch to Android platform (or use default name as it contains spaces - "New Unity Project (x)")
2. In Player Settings > Publishing Settings, create a new Keystone (Anywhere) and use it
3. Try building the application
Expected: application is built
Actual: errors are thrown, preventing application from being built
Reproduced in: 2019.2.0a1, 2019.2.0a10
Not reproduced in: 2017.4.25f1, 20118.3.12f1, 2019.1.0b10
Note: errors differ across the 2019.2 releases, most of them indicating that keystore cannot be found in the location provided.
Errors include:
"stderr[
Unexpected parameter(s) after input APK (Proj/yep.keystore)
]"
"UnityException: Can not sign the application
Unable to sign the application; keystore file not found!
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment