Cloud Build ignores provided keystore when making Development Build (2018.3.13f1)

Hi,

I uploaded my debug.keystore to Unity cloud build and selected it as my signing credentials.

It shows as "Valid" however "Keystore Information" shows "Debug: no" for some reason, and Cloud build does not sign my apk with provided keystore when "Development Builds" is set to "Yes" in advanced settings.

Switching "Development Builds" to "No" seems to solve the issue (however now I can't use debug functionality).

Here is my keytool output:

Code (CSharp):

1. $keytool -list -v -keystore debug.keystore -alias androiddebugkey -storepass android -keypass  android
2.  
3. Alias name: androiddebugkey
4. Creation date: May 20, 2018
5. Entry type: PrivateKeyEntry
6. Certificate chain length: 1
7. Certificate[1]:
8. Owner: C=US, O=Android, CN=Android Debug
9. Issuer: C=US, O=Android, CN=Android Debug
10. Serial number: 1
11. Valid from: Sun May 20 01:48:33 PDT 2018 until: Tue May 12 01:48:33 PDT 2048
12. Certificate fingerprints:
13.          MD5:  <removed>
14.          SHA1: <removed>
15.          SHA256: <removed>
16. Signature algorithm name: SHA1withRSA
17. Subject Public Key Algorithm: 1024-bit RSA key
18. Version: 1

When inspecting resulting apk, Development Builds seem to have "CERT.DSA" signature with Cloud Build certificate (instead of CERT.RSA which has the same SHA1 as my key).

The issue does not replicate when building locally.

 

Did you solve this?
We have similiar problem, but locally.
When we set "Development build" to YES, Unity uses ~/.android/debug.keystore instead of our custom keystore, provided in Build Settings

 

Was also having this issue and ended up just building locally. Was able to sign a Development Build via Android Studio (Build > Generate Signed Bundle / APK). I had not tried it with Unity's Android player settings. Android Studio also seems to not sign "debug" builds, so in the end I was only able to sign a Development(Unity)-Release(AndroidStudio) build.