Highlighted

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

Community Beginner ,
Apr 16, 2017

Copy link to clipboard

Copied

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.

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

Views

4.8K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

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

Community Beginner ,
Apr 16, 2017

Copy link to clipboard

Copied

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.

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

Views

4.8K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Apr 16, 2017 1
Adobe Community Professional ,
Apr 16, 2017

Copy link to clipboard

Copied

i think this is an animate cc 2017 issue on mac's.  is that what you're seeing?

if so, try animate cc 2015, Download and install Creative Cloud apps

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 16, 2017 0
Community Beginner ,
Apr 16, 2017

Copy link to clipboard

Copied

Win 7

tnx for link

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 16, 2017 0
Adobe Community Professional ,
Apr 16, 2017

Copy link to clipboard

Copied

i haven't seen that problem reported for win 7 but i would try 2015 anyway.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 16, 2017 0
Explorer ,
Apr 18, 2017

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 18, 2017 0
Adobe Employee ,
Apr 21, 2017

Copy link to clipboard

Copied

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

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 21, 2017 1
Adobe Employee ,
Apr 21, 2017

Copy link to clipboard

Copied

Hi,

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

Thanks!
Mohan

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 21, 2017 1
Community Beginner ,
May 23, 2017

Copy link to clipboard

Copied

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

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 23, 2017 0
Adobe Employee ,
May 23, 2017

Copy link to clipboard

Copied

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

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 23, 2017 0
Community Beginner ,
May 23, 2017

Copy link to clipboard

Copied

I installed 2017.1 and it works fine now.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 23, 2017 1
Community Beginner ,
May 23, 2017

Copy link to clipboard

Copied

I have Creative Cloud 4.0.1188 and it does not have "Previous Versions" submenu in "Filters & Versions" section.

Is there any way to convert p12 to format compatible with 2017.2 having same sha1 fingerprint? All android updates uploaded to google play console must have same sha1 fingerprint.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 23, 2017 0
Adobe Employee ,
May 23, 2017

Copy link to clipboard

Copied

Hi - Are you running a trial version of Creative Cloud? The trial version will not have that option.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 23, 2017 0
Community Beginner ,
May 23, 2017

Copy link to clipboard

Copied

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)?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 23, 2017 1
Adobe Community Professional ,
May 23, 2017

Copy link to clipboard

Copied

don't change your old p12; just save it. maybe a future animate version will allow you to use your old certificate.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 23, 2017 0
Adobe Employee ,
May 23, 2017

Copy link to clipboard

Copied

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

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 23, 2017 5
Contributor ,
May 27, 2017

Copy link to clipboard

Copied

Any update on this bug ? When can we expect to see a patch ?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 27, 2017 0
Adobe Employee ,
May 28, 2017

Copy link to clipboard

Copied

Hi,

The 1024 certificate created using ADT is not compatible with the latest Java and the fix cannot be done in AIR or Animate. Here is a KB article detailing the issue

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

Thanks!

Mohan

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 28, 2017 0
New Here ,
Jun 01, 2017

Copy link to clipboard

Copied

What's the process for getting it to work on a mac?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 01, 2017 0
Contributor ,
Jun 01, 2017

Copy link to clipboard

Copied

So, are we sure that in 3 or 5 years, The 1024 certificate will still be supported ? Because if we want to update our app on Google Play for the next years, we will still need our same 1024 certificate.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 01, 2017 0
New Here ,
Jul 19, 2017

Copy link to clipboard

Copied

Hi Monan,

thank you very much, you have also helped me a lot.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 19, 2017 0
Explorer ,
Jul 20, 2017

Copy link to clipboard

Copied

For what it is worth, this process does work, thank you.  It truly is just copying a JRE folder from a previous version and putting it in place of the current version.  It was painful, though, to spend all that time trying and testing and wondering what could be wrong with my settings/certificate/password, so I hope other users find this info sooner than I did.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 20, 2017 1
Community Beginner ,
Jul 31, 2017

Copy link to clipboard

Copied

I found that this method worked to a degree, but wasn't completely without problems. It seems like some issues were caused by ANEs, and this was causing errors when compiling (only with 1024RSA cert though).

In summary:

A: My app would compile fine on a new 2048 RSA (including all my ANEs).

B: By following the 'brute force' method, I could get it to compile on the old 1024 RSA but not with all ANEs running.

The ANE that seemed to trip it was either the Milkman storekit, or milkman google play services.

I do need these ANEs moving forward, though. So, to cut a long story short... after throwing a bunch of time and money at investigating and fixing it, I eventually just released a new version on new cert and took my licks. It kind of sucks to start over though, cos my old app had a good ratings history and some momentum... but you know...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 31, 2017 0
Community Beginner ,
Oct 17, 2017

Copy link to clipboard

Copied

I encountered this issue today (October, 2017). Funny thing is, five minutes ago I was able to publish to my testing iPad using a newly-generated certificate and brand-new provisioning profile. Then I shut down Animate CC.2017 and relaunched it. Tried to publish again, and now I'm getting the error.

But literally nothing has changed between those two attempts.

I seriously doubt installing cc.2015 and copying a jar file will fix this issue. What else could be at play here? It's a brand-new certificate that I issued today; it was working 5 minutes ago and now it's not after a restart of the application.

Any advice?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Oct 17, 2017 0
Community Beginner ,
Nov 15, 2017

Copy link to clipboard

Copied

Strangely, a shut down and reboot of the whole system (mac) actually solved this issue. I'm dumbfounded, but happy to have been able to release the app.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 15, 2017 0
Contributor ,
Mar 14, 2018

Copy link to clipboard

Copied

I'm also having this problem with Milkman ANE. Has anyone figured out how to fix that? Would migrating to FlashBuilder help?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 14, 2018 0
Adobe Community Professional ,
Mar 15, 2018

Copy link to clipboard

Copied

i've never had a problem with a milkman ane unless using an older version.  if you can confirm, there is no problem when you do not include the ane and there is a problem when the ane is included, first make sure you're using the latest version.  then write to milkman.  they are very responsive.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 15, 2018 0
Contributor ,
Mar 15, 2018

Copy link to clipboard

Copied

I'm using the billing ANE. This is the warning that I get this from Google Play:

Warnings

You uploaded an APK that does not have BILLING permission, or has a BILLING permission that is limited to specific sdk versions. BILLING permission is required for selling in-app products.

So this confirms ridic blayze's experience.

As far as contacting milkman, of course I had done that before posting here. Have not heard back from them.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 15, 2018 0
Adobe Community Professional ,
Mar 15, 2018

Copy link to clipboard

Copied

Hi.

Does your app manifest (.xml) has this line between the <manifestAdditions> tags?

<uses-permission android:name="com.android.vending.BILLING" />

__________________________________________
HTML5, JSFL, and AS3 samples: http://bit.ly/2mJgDoG

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 15, 2018 2
Adobe Community Professional ,
Mar 15, 2018

Copy link to clipboard

Copied

i'm using the milkman billing ane on google play and submitted an app last month without problem.  and most likely you're using an incorrect permissions tag or omitted it.  ie, see message 29 and include the ane in your extensions tag:

  <extensions>

    <extensionID>com.milkmangames.extensions.AndroidIAB</extensionID>

  </extensions>

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 15, 2018 2
Contributor ,
Mar 15, 2018

Copy link to clipboard

Copied

Thank you! That was the problem. I had

   <uses-permission android:name="com.android..BILLING" />

I don't know how that line got corrupted. In any event, thank you so much for your suggestion. It's good to know that milkman stuff still works.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 15, 2018 1
Community Beginner ,
Apr 08, 2019

Copy link to clipboard

Copied

Here in April 2019, the brute force method described by @Mohanaraj no longer works.

Copying the old version of Java does allow for the APK to be built in Adobe Animate or via the command line. But when the APK is submitted to the Google Play Store, you'll get a message that "the certificate doesn't match the SH1 fingerprint on file".

Because of this I'm unable to update an older app in the Play Store and there's a critical bug I need to fix. I've tried to migrate to Google's App Signing service but I can't convert my old certificate because it's 1024bit. Google rejects the conversion because it doesn't meet a minimum encryption standard.

Has a non-brute force resolution been found for this? My app has close to a million downloads, so I'm not going to create a new app. I need to update the existing one. This problem has been known for close to two years now, I'm surprised there still isn't a ready-made solution. It's things like this that make me no longer recommend Adobe Air to new clients because Adobe isn't keeping up with maintaining compatibility.

Hope I'm wrong on this and there's a fantastic solution posted somewhere that I've overlooked.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 08, 2019 0
Community Beginner ,
Jun 30, 2017

Copy link to clipboard

Copied

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).

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 30, 2017 0
Community Beginner ,
May 25, 2018

Copy link to clipboard

Copied

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?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 25, 2018 0