Today I didn’t sign the application with the key ... What led to the following error on the server (in Google Play Consol'e):
Download failed The downloaded APK file is signed with a certificate that is different from the one you specified. Digital print of your certificate:
...
...
I want to share a solution to the problem!
It turned out, forgot alias from the correct key. In the beginning I thought that problems with choosing a key ...
The alias to one or another key can be recognized using the command (entered on the command line):
keytool -v -list -keystore PATH \ your_key.jks
For example,
keytool -v -list -keystore D:\YOUR_FOLDER\your_key.jks (ask for password ...)
After entering the 'computed' alias, everything was signed and published normally ...)
PS Taking this opportunity, I want to note that it is advisable to store copies of keys from each application on external media (better than several, because if the key is lost, the application can no longer be updated on the Google Play Store) ... and somewhere in a notebook write what keys and aliases signed applications.
This message was written after the site asked to share personal experience, which I do with great pleasure! )
alias can also be found by opening the jks file of your application. It is clearly indicated there among other unreadable characters. 
Source: https://ru.stackoverflow.com/questions/847026/
All Articles