I published the application with the SHA 1 debug key, then tried to upgrade with the release key. The console does not accept updates, requires the old key. Do you really have to make a copy of the project with the release key and re-upload it to the console? Can I sign an application with both release and debug keys at the same time?

    1 answer 1

    Headline Response:

    No, It is Immpossible. One application - one key (certificate for signing).

    The answer is essentially the problem:

    It is impossible to put an application with a key in the market - it has a validity period of only 365 days , and the market accepts applications signed with certificates valid for at least 25 years .

    Thus, you did not post the application with the same key, but with a completely release version (at least this key has a validity period of 25+ years).

    If you can not find this key then yes - you have a problem. Unsolvable. You will have to create a new application in the console with a different package and a new key for signing.

    On the other hand, you may have encountered a problem of a different kind - you have uploaded an application with the signing of an APK file on the Google side by Google itself. (this is a solution recently promoted by Google, which can be abandoned only by pressing a lot of buttons and which cannot be canceled by agreeing once (for each application this mechanism is activated separately)). If this is your case, then all is not lost - to sign the application on your side, you do not use the release certificate, but the boot key, which can be changed by contacting those. Google support via the console. If this is not your case, then only a new application with a new package and a new signature key.

    • The application with Google authentication. The checksum of the SHA 1 certificates I have created in the keytool is not a release and the google-services.json file is added to the application with this checksum. The application on the emulator works correctly, and downloaded from the market does not pass authentication. - Ruslan Chepizhko
    • @RuslanChepizhko, if your problem is not the loss of a key, but the fact that debug Apk passes authorization, but the release version does not, then the fact is that there is no imprint of the release key in google-services.json . In this case, it must be added to it (if it was done there in the FirebaseConsole , otherwise - from where the file was downloaded). After that, you need to re-download google-services.json , update it in the project (better - copy-paste content, not by replacing the file), build the APK again and update it in the developer console. - YurySPb ♦
    • And google-services.json can add both debugging and release SHA 1? Or first you need to delete debazhny key? - Ruslan Chepizhko
    • @RuslanChepizhko, you can both this and that. And some more. No restrictions - YuriySPb ♦
    • one
      Everything fell into place. Thank! - Ruslan Chepizhko