apk has been signed with a different certificate to previous apks (intune/google play)

[stephannn]

Hi,

trying to upload the latest APK version 1.3.0 into intune combined with google enterprise store, we receive the following error: apk has been signed with a different certificate to previous apks

On the RustDesk-Server the package name is the same. Also verifying the certificate of the old and the new APK look identically: 1.3.0:

subject=C = SG, ST = SG, L = SG, O = PURSLANE, OU = RustDesk, CN = Zhou Huabing
issuer=C = SG, ST = SG, L = SG, O = PURSLANE, OU = RustDesk, CN = Zhou Huabing

1.2.7:

subject=C = SG, ST = SG, L = SG, O = PURSLANE, OU = RustDesk, CN = Zhou Huabing
issuer=C = SG, ST = SG, L = SG, O = PURSLANE, OU = RustDesk, CN = Zhou Huabing

The error in intune is:

When we try to upload the APK into google play we get following error:

Upload failed You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint:
[ SHA1: D9:6F:2D:6F:DE:7F:44:B9:93:F2:72:49:94:87:2A:9C:2A:36:1D:FD ]
and the certificate used to sign the APK that you uploaded have fingerprint:
[ SHA1: D8:0F:4B:EB:94:48:22:0E:B1:E1:1F:AB:78:55:02:A1:80:3D:B0:05 ]

We did not signed the APK ourself, it was signed by the server. Any idea what we are doing wrong?

Thanks Stephan

[rustdesk]

My mistake, please build a new one.

[stephannn]

Thanks for the quick fix! It worked.

[stephannn]

Fix worked