Cloud build APK jar signer fail

Unity Services
1

Hello, I’m having issues cloud build. Prior to 2017 we had no problems having our APK signed, but now our APK signing is failing. I’ve included the error cloud build is sending. I’ve also removed the password that cloud build prints out.

CommandInvokationFailure: Failed to sign APK package.
34968: [Unity] /APPLICATION_PATH/Android Studio.app/sdk/build-tools/25.0.3/apksigner sign --ks “/BUILD_PATH/v2games.ga.0-dev-android-1/bvr/CLOUD_BUILD_APPKEY_REMOVED.keystore” --ks-pass pass:“PASSWORD” --ks-key-alias “KEY_ALIAS” --key-pass pass:“PASSWORD” “/BUILD_PATH/v2games.ga.0-dev-android-1/Temp/StagingArea/Package.apk”
34969: [Unity] stderr[
34970: [Unity] Unexpected parameter(s) after input APK (gakey --key-pass pass:)
34971: [Unity] ]
34972: [Unity] stdout[
34973: [Unity] ]
34974: [Unity] exit code: 1
34975: [Unity] at UnityEditor.Android.Command.Run (System.Diagnostics.ProcessStartInfo psi, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg) [0x00000] in :0
34976: [Unity] at UnityEditor.Android.PostProcessor.Tasks.TasksCommon.Exec (System.String command, System.String args, System.String workingdir, System.String errorMsg, Int32 retriesOnFailure) [0x00000] in :0

This is really important to us to resolve quickly as we are requiring to send a build to our publishers soon and this is causing testing problems.

Some extra info maybe it can help
Unexpected parameter(s) after input APK (gakey --key-pass pass:)
we do have an ‘=’ in our password. We used a random generator. The password was working for 13 months. Only today with 2017 did it stop.

2

Does signing work locally in that same version of Unity and same keystore/pass combo? Unity Cloud Build isn’t doing any extra signing, just injecting the keystore and alias/passwords into the PlayerSettings at build time and letting the editor handle signing as part of its normal build process.

3

My apologies for not replying earlier. We have our numerous technical issues.

Sorry, signing does not work locally either.
Since then we found a stack overflow solution to change the password. This has solved our problem. This seems to have occurred updating our google sdk tools version.