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.
i haven't seen that problem reported for win 7 but i would try 2015 anyway.
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.
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.
This is an AIR issue with the latest Java update. AIR team looking into it.
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
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
I installed 2017.1 and it works fine now.
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.
Hi - Are you running a trial version of Creative Cloud? The trial version will not have that option.
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)?
don't change your old p12; just save it. maybe a future animate version will allow you to use your old certificate.
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
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.
Any update on this bug ? When can we expect to see a patch ?
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
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.
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.
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.
What's the process for getting it to work on a mac?
thank you very much, you have also helped me a lot.
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.
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).
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...
I'm also having this problem with Milkman ANE. Has anyone figured out how to fix that? Would migrating to FlashBuilder help?