Skip to main content
O
oriumgames
Inspiring
April 16, 2017
Answered

“Could not access the digital certificate. unable to load a certificate in this file”

  • April 16, 2017
  • 11 replies
  • 9281 views

Ok im started new thread cause existed was marked as solved.

I cant publish android apk with my old certificate. But i need this cause i cant update my old android games with new created certificates.

Dear Adobe team can you say how much time you need to fix this? Im not alone.

    This topic has been closed for replies.
    Correct answer Mohanaraj

    I installed 2017.1 and can build android app with an old certificate.

    What can I do with my p12 certificate if I want to use future versions of Adobe Animate (2017.2+) for making updates to my android application (same sha1 fingerprint)?


    Hi,

    In case if you want to use Animate CC 2017 with the old 1024 RSA certificate then you can do the following

    Prerequisite: Install Animate CC 2015.2 so that you have the older version of Java installed at

    C:\Program Files\Common Files\Adobe\Adobe Animate CC 2015.2\jre

    Steps:

    1. Quit any version of Animate if it is running

    2. Copy C:\Program Files\Common Files\Adobe\Adobe Animate CC 2015.2\jre

    3. Rename C:\Program Files\Common Files\Adobe\Adobe Animate CC 2017\jre folder to say C:\Program Files\Common Files\Adobe\Adobe Animate CC 2017\orig_jre

    4. Paste the jre folder that you have copied in step 2

    5. Launch Animate CC 2017 and publish your android app using the older 1024 RSA certifcate

    Please note that this is just a brute-force method and not a certified/recommended workflow.

    Thanks!

    Mohan

    11 replies

    M
    mostafa hibashi
    Participant
    August 7, 2020

    شكرا جزيلا 

    جزاكم الله خيرا

    thank you

    D
    dustin_bahr
    Known Participant
    July 31, 2019

    I figured out a workaround here: Re: Getting "unable to load a certificate in this file" when trying to publish APK

    D
    dustin_bahr
    Known Participant
    July 31, 2019

    How do you install Animate 2015.2 these days. Creative Cloud doesn't give me the option.

    kglad
    Community Expert
    kgladCommunity Expert
    Community Expert
    July 31, 2019

    check one of your duplicate posts, Re: Getting "unable to load a certificate in this file" when trying to publish APK

    D
    dustin_bahr
    Known Participant
    July 31, 2019

    Having this in Animate 2019 on MacOS 10.14.3 (Mac OSX).

    What is the solution for Mac?

    I have attempted to downgrade to Java (build 1.8.0_74-b02). No luck, same message.

    This is 100% ridiculous.

    From the very first time Adobe created a certificate for me through the Flash interface, many years ago, there was something in the back of my head that said, this just doesn't feel right. Well, here we are years later getting screwed.

    imacroi32160956
    imacroi32160956
    Participant
    February 6, 2019

    i have the same problem.

    i finished editing my app in adobe animate and when i go to publish, it forces me to enter my digital signature. When i press on create new and fill the form, a long error message appears.

    could you please help generating a digital signature.

    Thanks.

    kglad
    Community Expert
    kgladCommunity Expert
    Community Expert
    February 6, 2019

    what error?

    ozmachine
    ozmachine
    Known Participant
    November 15, 2017

    I was suffering the same issue, but using Google's App Signing solution, we can get around the incompatibility issue by creating a new key to publish with. You will need your original key, and follow their instructions. It was a bit of work, but now it works well for me.

    Manage your app signing keys - Play Console Help

      R
      ridic blayze
      Participating Frequently
      June 30, 2017

      I'm fairly pissed about this whole thing... and I doubt that i am alone - i.e. this bug surely affects anyone who published an app on the google play store that is more than a couple of years old, and in my experience, it makes it near impossible to update them as you cannot change certs without creating a new app listing.

      Besides that, the fix doesn't work like it should. Despite following the steps above, I still get problems. This fix worked for me once...  but now i can't get it to work again, despite uninstalling / reinstalling animate cc 2015.2, and following the steps.

      Only thing I can think of is using air sdk 22, but .... after downloading, 2015.2 is telling me the sdk is invalid (or any other sdk for that matter), and if i try to add the sdk in 2017 version, it says it cannot handle any sdks below 25!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

      Now, when I compile, I get this error:

      Error from apksigner: ERROR (Jar signer CERT.RSA): Failed to verify JAR signature META-INF/CERT.RSA against META-INF/CERT.SF: java.security.SignatureException: Certificate has unsupported critical extension(s)

      I've noted that if I use a 2048 cert, it compiles fine (but that's no good to me, of course).

      P
      PapaDeBeau1234
      Participant
      May 25, 2018

      I am in great pain. I too can not update an older app. Is there a resolve to this? In face I can't even upload any app because I keep getting this error.Error from apksigner: ERROR (Jar signer CERT.RSA): Failed to verify JAR signature META-INF/CERT.RSA against META-INF/CERT.SF: java.security.SignatureException: Certificate has unsupported critical extension(s)

      How can we fix this so I can update or publish new apps?

      M
      Maks_T
      Participant
      May 23, 2017

      I have same issue on Adobe Animate 2017.2 on Windows 10 x64 with JRE-32 8u112 installed

      Creative Cloud does not allow to install CC 2015 or 2017.1

      Mohanaraj
      Adobe Employee
      Mohanaraj
      Adobe Employee
      May 23, 2017

      Hi,

      Have you tried installing 2015.2 using the steps provided at Download and install Creative Cloud apps ?

      Here is a KB article detailing the issue

      https://helpx.adobe.com/x-productkb/multi/rsa1024-certificate-issue-with-adt-tool.html

      Thanks!

      Mohan

      Mohanaraj
      Adobe Employee
      MohanarajCorrect answer
      Adobe Employee
      May 23, 2017

      I installed 2017.1 and can build android app with an old certificate.

      What can I do with my p12 certificate if I want to use future versions of Adobe Animate (2017.2+) for making updates to my android application (same sha1 fingerprint)?


      Hi,

      In case if you want to use Animate CC 2017 with the old 1024 RSA certificate then you can do the following

      Prerequisite: Install Animate CC 2015.2 so that you have the older version of Java installed at

      C:\Program Files\Common Files\Adobe\Adobe Animate CC 2015.2\jre

      Steps:

      1. Quit any version of Animate if it is running

      2. Copy C:\Program Files\Common Files\Adobe\Adobe Animate CC 2015.2\jre

      3. Rename C:\Program Files\Common Files\Adobe\Adobe Animate CC 2017\jre folder to say C:\Program Files\Common Files\Adobe\Adobe Animate CC 2017\orig_jre

      4. Paste the jre folder that you have copied in step 2

      5. Launch Animate CC 2017 and publish your android app using the older 1024 RSA certifcate

      Please note that this is just a brute-force method and not a certified/recommended workflow.

      Thanks!

      Mohan

        Mohanaraj
        Adobe Employee
        Mohanaraj
        Adobe Employee
        April 21, 2017

        Hi,

        This is an AIR issue with the latest Java update. AIR team looking into it.

        Thanks!
        Mohan

        C
        chasbln
        Known Participant
        April 19, 2017

        Same problem on OSX. I think we should stop working with Adobe Air! Last night I had to update some apps. It takes hours of time to install working SDKs and CC versions. In one of my apps all buttons are deactivated after updating to SDK 23-25. CC 2017 doesn't load old certificates. After export nothing works. The best working combination was CC 2015 and SDK 22. One of my apps must be delete from store now cause there's no way to downgrade it again.

        PLEASE GIVE US AN UPDATE.

        Preran
        Community Manager
        PreranCommunity Manager
        Community Manager
        April 21, 2017

        Hi everyone,

        I checked with the teams and they have logged a bug for it and it is under investigation. I will post here if I receive additional info.

        Thanks,

        Preran

        Show more replies
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices