please increase versionCode with each release

[IzzySoft]

versionCode for 1.0.4 is 2 – as it was for 1.0.3 (and probably even before), so Android doesn't see this version as an update and people miss out on it. Can you please take care to always increase versionCode when making a new release? That's what Android uses internally to tell versions apart. Thanks in advance!

[IzzySoft]

Further, certificates do not match so no upgrade is possible. 1.0.3 had:

package: name='fr.themsou.monitorinternetless' versionCode='2' versionName='1.0.3' platformBuildVersionName='13' platformBuildVersionCode='33' compileSdkVersion='33' compileSdkVersionCodename='13'
Verifies
Verified using v1 scheme (JAR signing): false
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): false
Number of signers: 1
Signer #1 certificate DN: CN=Clement Grennerat, L=Grenoble
Signer #1 certificate SHA-256 digest: 02c708329a21a830ba81a119e46960c01d29a47ea903d9ffa9b6091a6a5421b8
Signer #1 certificate SHA-1 digest: b64001d0492559eb6622c35cf51795a04fcd5a66
Signer #1 certificate MD5 digest: aeec09b5558f6213b96f4bb341b5b165
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 public key SHA-256 digest: 83675758980cf3b9dc54c5052a6c738e6b1cf07a851f2e44b63921c13ba792b4
Signer #1 public key SHA-1 digest: e03a84ea5ec410e9d9624afb540dcea3e2cdb68d
Signer #1 public key MD5 digest: f5d2cc67470b50a123d6ce0afb6a5b57

1.0.4 comes with

package: name='fr.themsou.monitorinternetless' versionCode='2' versionName='1.0.4' platformBuildVersionName='14' platformBuildVersionCode='34' compileSdkVersion='34' compileSdkVersionCodename='14'
Verifies
Verified using v1 scheme (JAR signing): false
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): false
Number of signers: 1
Signer #1 certificate DN: C=Fr, ST=France, L=Grenoble, CN=Clément Grennerat
Signer #1 certificate SHA-256 digest: 98d6faab69fe1aabf74421533a10f4e182bd24f9f2b138bbafb73109cb78f6b5
Signer #1 certificate SHA-1 digest: 2b4d30298fc7e05f6060c249d6bea285f38f674b
Signer #1 certificate MD5 digest: 43396edc51d50f6dc222476c8cc00be7
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 public key SHA-256 digest: fe38b5a8016d244ba3c06605afd7ec53bdf1015e74f860d39fb5d42b53f5e6e9
Signer #1 public key SHA-1 digest: c5142ecca7b995fc4e3d1f1fcb61c11c3d07f4c0
Signer #1 public key MD5 digest: a4ed9b44df1d2ec29c0d8a69fc40554b

What happened to the original key?