Upload failed

Discussion in 'Showcase' started by Malek Soualmia, Feb 11, 2016.

  1. Malek Soualmia

    Malek Soualmia New Member

    Joined:
    Mar 4, 2015
    Messages:
    6
    Likes Received:
    2
    I GOT THE BELOW ERROR WHEN I AM TRYING TO UPLOAD MY APPYET APPLICATION ON GOOGLE PLAY. PLEASE ADCVICE AND THANKS:

    Upload failed

    You uploaded an APK that is signed with an insecure certificate. RSA or DSA key size must be at least 2048 bits.

    ATTACHED A SCREEN SHOT
     

    Attached Files:

    #1
  2. soufiane

    soufiane New Member

    Joined:
    Feb 11, 2016
    Messages:
    2
    Likes Received:
    1
    I board the same problem! I think there is a problem on the site
     
    #2
    Malek Soualmia likes this.
  3. Malek Soualmia

    Malek Soualmia New Member

    Joined:
    Mar 4, 2015
    Messages:
    6
    Likes Received:
    2
    I HOPE SO :)
     
    #3
    soufiane likes this.
  4. Malek Soualmia

    Malek Soualmia New Member

    Joined:
    Mar 4, 2015
    Messages:
    6
    Likes Received:
    2
    Any one can help please?

    Sent from my SM-N900 using AppYet
     
    #4
    soufiane likes this.
  5. DarShaN PanDya

    DarShaN PanDya Active Member

    Joined:
    Dec 11, 2015
    Messages:
    580
    Likes Received:
    104
    You can Sign the App with another Certificate!
    But the Problem is, You will have to Sign it everytime you upload an Update App!

    If u don't want this then You'll have to wait untill AppYet (admin) is Back!
     
    #5
  6. SplendorMagic

    SplendorMagic New Member

    Joined:
    Feb 12, 2016
    Messages:
    5
    Likes Received:
    1
    """""""""""""""""

    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
     
    #6
  7. SplendorMagic

    SplendorMagic New Member

    Joined:
    Feb 12, 2016
    Messages:
    5
    Likes Received:
    1
    Good News

    problem solved for me. just reuploaded the apk file. you can try again now
     
    #7
    soufiane likes this.
  8. soufiane

    soufiane New Member

    Joined:
    Feb 11, 2016
    Messages:
    2
    Likes Received:
    1
    yeeeeeeeess yes problem solved :D
     
    #8
  9. DarShaN PanDya

    DarShaN PanDya Active Member

    Joined:
    Dec 11, 2015
    Messages:
    580
    Likes Received:
    104
    Great News! :D
     
    #9

Share This Page