Hi,
I run into a strange problem. I built a standalone AIR application for Windows desktop with embedded AIR player (3rd Option in "Export as"...).
I'm on a Windows 10 64 Bit system with all current updates. My Animate CC 2017 is updated today to the Dec. 2016 release and I downloaded the AIR SDK 24 as well and added this to my available SDK options. It now shows up in Animate as it should.
So far, I'm struggling to sign the exe-file in a proper way. There is no error message, but if I check the file property of my executable file:
AIR SDK 23: either there is no digital signing (this happens when I assign one or more app icons/symbols) ORthere is a digital signing but from Adobe Systems Inc. (sha1) instead of showing up the properties of my P12/PFX certificate (this happens if I remove all assigned icons).
AIR SDK 24: it doesn't matter if I assign icons or not, the executable stays unsigned.
I tried it as well with generating a local certificate inside of Animate CC with no success.
If I try an external signing tool, to add my signature later on, it says file is already signed. As far, I found only two solutions:
1. Use SDK 23 and remove all app icons, get an pseudo Adobe Inc. signature, override signature with an external signing tool it replace it with the right one.
2. Use any SDK, include app icons and use an external tool to remove invisible (not showing up in file properties) signature and get an unsigned exe. Then sign it as in 1 with my external tool.
Is there any way to do it in a proper way? Why is the signing process not working as expected. What are the reasons for this dependency?
Any help would be greatly appreciated.
Carsten
