Thanks Bill: The confusion on my part was thinking I could use a MacOS application code-signing certificate from the Apple Developer program to sign a Desktop AIR app for MacOS--but it appears you cannot!
All instructions I've found from Adobe and the many stack overflow and other forum posts never mention this, they just say that you can code-sign with any code-signing cert from a certificate authority, and of course Apple is a CA, but their cert won't sign an AIR app for MacOS. Weird but apparently true. We've since ordered a code-signing certificate especially for AIR desktop apps for Windows and MacOS from DigiCert ($200!) which is supposed to work, but I haven't received it yet. They are taking their time verifying our identity. Hopefully I'll have it this week and I will post the solution once I get it working. Also, found a couple things others may find valuable if porting a mobile to Desktop AIR: It is possible to reuse AS libraries that reference ANEs for mobile in the desktop project, there's a trick but it works even if the ANE doesn't work on desktop. This makes it easy to just reuse the same codebase for mobile and desktop. If you use StyleableStageText in a mobile project, you cannot reuse that code on desktop unless you add mobilecomponents.swc as an external library dependency. With these two points, I am sharing 98% of my mobile app's codebase with the desktop project just using shared libraries. Took a bit of effort to figure these things out but it's awesome to get desktop almost for free, except for these dumb code-signing issues. Cheers, Erik On Aug 21, 2018, at 10:45 AM, bilbosax <[email protected]> wrote: Erik, I don't know a lot about these things, but this is one I think I would send over to the Adobe AIR forums. They seem to have their hands more on the mechanics of compiling and packaging than I think the guys over here at Flex probably do. Just a thought. -- Sent from: http://apache-flex-users.2333346.n4.nabble.com/
