1. Check Tools - Private Sign Key. Look for the public key algorithm. If it isn't an old key then it should show 2048-bit RSA key.
2. Assuming that this is the case, add this line:
The page on my console just ask to load an app bundle. If I try to load an apk I get this message that says to load a valid app bundle:
Anyway, I opened a ticket on googleplay-developer-support@google.com
1. Check Tools - Private Sign Key. Look for the public key algorithm. If it isn't an old key then it should show 2048-bit RSA key.
2. Assuming that this is the case, add this line:
1. Check Tools - Private Sign Key. Look for the public key algorithm. If it isn't an old key then it should show 2048-bit RSA key.
2. Assuming that this is the case, add this line:
1. Check Tools - Private Sign Key. Look for the public key algorithm. If it isn't an old key then it should show 2048-bit RSA key.
2. Assuming that this is the case, add this line:
1. Check Tools - Private Sign Key. Look for the public key algorithm. If it isn't an old key then it should show 2048-bit RSA key.
2. Assuming that this is the case, add this line:
1. Check Tools - Private Sign Key. Look for the public key algorithm. If it isn't an old key then it should show 2048-bit RSA key.
2. Assuming that this is the case, add this line:
Tested right now. It works perfectly, thank you!!!
About the ticket .... no news from google yet, but I hope it can be useful to let them understand that it could be nice to have warnings about further changes.
Tested right now. It works perfectly, thank you!!!
About the ticket .... no news from google yet, but I hope it can be useful to let them understand that it could be nice to have warnings about further changes.
To open a ticket I click on the question mark in the top right corner of the developer's console. This action opens a guide, and in the guide clicking on "contact us" one has to provide the information needed to open a ticket.
About loading APKs I found this: https://support.google.com/googleplay/android-developer/answer/9842756?hl=en
At the point "How it works--> Note" there is some information. They suggest to use their Play App Signing. Don't know, up to now the key signature generated by B4A works perfect for me.
No. There are no benefits for AABs. At least not with B4A. If you want to waste your time and energy then ask Google to upgrade your key (the old key isn't compatible with their new requirements). Eventually the result will be exactly the same.
Bottom line:
1. If using old key - submit an APK.
2. If using new key - add the #SignKeyAlgorithm