Search Issue Tracker
Fixed in 2017.1.0f3
Votes
2
Found in
2017.1.0f1
Issue ID
925940
Regression
Yes
The project does not build on the device and an error "Win32Exception" appears when the key is set in Player Settings
Reproduction steps:
1. Create a new project;
2. Switch platform to Android;
3. Go to Player Settings -> Publishing Settings;
4. Create a new Keystore;
5. Set the new Keystore to Key settings;
6. Build the project;
Actual result: the project does not build on the device. An error appears "Win32Exception: ApplicationName='E:\AndroidSDK\build-tools\26.0.0\apksigner.bat', CommandLine='sign --ks "E:/Downloads/Key And Keystore Test (1)/user.keystore" --ks-pass pass:"111111" --ks-key-alias "toma"".
Expected result: an error should not appear and the project should be built.
Reproduced with: 2017.1.0a3, 2017.1.0b1, 2017.1.0f3, 2017.2.0b2
Not reproducible with: 5.5.4p1, 5.6.2p3, 2017.1.0a2
Regression introduced in 2017.1.0a3
Note: the issue is not reproducible with the newest Android SDK Build-Tools (26.0.1)
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
- [Android] Soft keyboard is missing the "OK" button on Android
- The Profiler ignores a modified targetFrameRate when profiling Edit mode
- [General] Package manager takes 15 minutes to load
- Asset's Inspector information is no longer displayed when docking the Search Window
- Crash on Object::GetCachedScriptingObject when entering Play Mode
aboazar
Oct 06, 2017 18:29
Yes indeed updating to Android SDK Build Tools v.26.0.1 fixes it, thanks JOKERMINATOR.
Ekwav
Aug 15, 2017 15:37
JOKERMINATOR is right :)
Jokerminator
Jul 26, 2017 09:31
Updating to Android SDK Build Tools v.26.0.1 fixes the issue. :)