"""""""""""""""""
I just contacted Google Support about this and they said the following:
Currently there is an internal bug which is the cause for this issue. I'm very sorry for the inconvenience, however there currently isn't any update on the matter as of yet.
They said they would email me with an update once there is one and I will post it here when I receive the email.
"""""""""""""""""""
I would suggest not generating a new certificate if you've already published apps with the current one you are attempting to use.
I contacted Google Support, and they did confirm that this was a bug. I did a live chat, and that person mentioned its a bug they started seeing today, and no action is required on my part. He couldn't tell me when it ll be fixed.
I noticed that I was able to upload an APK to an existing app with the non 2048 bit release key, and it only complained for a new app.
"""""""""""""""""""
source :
http://stackoverflow.com/questions/...pk-that-is-signed-with-an-insecure-certificat