Android Question Troubles uploading APK with Play App Signing

[mcorbeel]

Since I replaced my computer I am not able to upload an APK to the Google app store. I read this article:

Google Play App Signing

Google Play App Signing service allows developers to let Google store the app signing key for them. Developers need to use a different key, the upload key, to sign the app before release. The advantage of this service is that with the help of Google support you can generate a new upload key in...

www.b4x.com

and it starts by saying that I must upload my original key to Google and that "The encryption key should be replaced with the key from the instructions page"
The thing is that on the Google instruction page I don't see any key. I only see some fingerprints and 2 certificates that I can download: a app-singing certificate and one upload certificate.
How can I continue?

 

[mcqueccu]

Don't use google play app signing

 

[mcorbeel]

Don't use google play app signing

Once enabled apparantly it cannot be disabled...

 

[Computersmith64]

Don't use google play app signing

Why? I don't have any issues with it.

 

[Erel]

Question is not clear. Have you lost the original key when you replaced computers?

 

[mcorbeel]

I guess that the key is a file, is that correct? I still have my old computer so nothing is lost. What I found is a file called androidkey.keystore, Is that it? Or how can I check that this is the required key?

 

[DonManfred]

a file called androidkey.keystore, Is that it?

Possible

Or how can I check that this is the required key?

Try to load that file in the IDE (sign keys (Load existing Key)) providing the correct password for this file.

 

[mcorbeel]

Yes I tried this and I get this (replaced some confidential text with xxxxxxx):

Keystore type: jks
Keystore provider: SUN
Your keystore contains 1 entry
Alias name: b4a
Creation date: Nov 10, 2012
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=Marc Corbeel, O=Echo bvba, C=BE
Issuer: CN=Marc Corbeel, O=Echo bvba, C=BE
Serial number: 5110c40d
Valid from: Sat Nov 10 16:26:24 CET 2012 until: Sat Mar 11 16:26:24 CET 2051
Certificate fingerprints:
SHA1: 14:CD:EB:9D:E0:4C:84:3C:Axxxxxxxxxxxxxxxxxxxxxxxxxxx
SHA256: AF:16:AA:8D:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Signature algorithm name: SHA1withDSA (weak)
Subject Public Key Algorithm: 1024-bit DSA key (weak)
Version: 3
Extensions:
#1: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: EA 77 2xxxxxxxxxxxxxxxx .w/.'......V%..K
0010: 9A D8 5E BE ..^.
]
]
*******************************************

 

[Erel]

We can't say whether it is the key that you previously used.

We also can't say what has changed and why replacing a computer caused you problems. Only you know what has changed.

 

[mcorbeel]

To be sure, I now went back to my old computer (where everything worked before). I compiled the new project version and uploaded the apk to Google. The upload now works without returning an error. (Why this gives an error when I do exactly the same on my new computer I would like to know). But in the Google release page of my app I now see

Je kunt deze release niet implementeren omdat de release niet toestaat dat bestaande gebruikers upgraden naar de onlangs toegevoegde APK's

which means something like

You cannot implement this release because the release doesn't allow users to upgrade to the recently added APK's

So what is wrong here (besides me obviously knowing too little ;-))?

 

[mcorbeel]

This is the message translated with Google translate:

You cannot deploy this release because the release does not allow existing users to upgrade to the recently added APKs.

 

[mcorbeel]

Okay, found the issue. My new version had a version number that is smaller that the production version. Pitty that Google didn't say this in the first place.