Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
re-cycle
Explorer
re-cycle
Explorer
Activity
‎Sep 22, 2019
10:55 AM
Not come across this myself but googling around it seems that codesign ambiguous error often relates to having two certificates in Keychain with the same ID: https://stackoverflow.com/questions/32925844/codesign-and-ambiguos-identity-matches-mac-developer-and-iphone-developer
... View more
‎Jul 26, 2019
03:47 AM
5 Upvotes
I have it working!!! Woooohoooo! DHL83​'s correspondence with Apple and reference to the Electron thread on Apple's Developer support site provided me with some ideas for googling whether entitlements could be added for apps produced by 3rd party tools such as the Flex SDK. After a lot of trial-and-error, I worked out what entitlements are required. Here are the steps in addition to the signing script I posted above: 1. You need to create an Entitlements file which will look like this: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>com.apple.security.cs.allow-jit</key> <true/> <key>com.apple.security.cs.allow-unsigned-executable-memory</key> <true/> </dict> </plist> Thismust be created in XCode otherwise get an error about blobs not being correct: HomeDirXCodePropertyList.plist: unrecognized blob type (accepting blindly) HomeDirXCodePropertyList.plist: invalid length in entitlement blob To create in XCode, do this: In XCode, File->New->File... Choose MacOS tab -> Resource -> Property List Right click on the document -> Property List Type -> Entitlements File Add Row using + button. Select Allow Execution of JIT-compiled code and select Boolean value YES Add Row using + button Select Allow Unsigned Executable Memory and select Boolean value YES Save the file (I called it entitlements.plist) and reference it in the .app signing line. 2. Change the script you use for signing the .app to reference this file: codesign --force --options runtime --deep --sign "Developer ID Application: My Company, Inc (AB1CD2E3FG)" --entitlements "/Users/username/Documents/entitlements.plist" "/Users/username/Documents/out/MyApp.app" Check that you don't get any errors from the entitlements file. 3. Use product build in the script as before (no changes) to create the .pkg 4. As before, submit the app for Notarization, then staple once it completes successfully. My testing has been as follows: 1. Delete the .app files from my machine. 2. Upload the .pkg file to a web server. 3. Download it and install on 10.14.5 Mojave. It installs and runs without the previous codesign error. Hope it works for others!
... View more
‎Jul 24, 2019
07:35 AM
2 Upvotes
Ah, so we're helpless unless someone at Adobe who wrote the code for the ADT tool will help us by talking directly to Apple. Actionscript has always been Just In Time compiled as far as I know and if Apple are saying that's the reason for the notarization failing then it's a problem at the very core of the AIR runtime which Apple have introduced by requiring notarization. Does anyone have a clue about how to get an Adobe engineer to look at this? I'm guessing it would need someone from a large company who have a big support contract with Adobe to have enough clout for them to sit up and take notice... ;-( DHL83 - thanks very much for reporting back with this. Anyone have any other ideas about how to work around this?
... View more
‎Jul 22, 2019
04:56 AM
Just some quick additional information: this doesn't seem to be restricted to AIR: there are users of other platforms reporting the same issue (without solutions yet...) e.g. Unity: https://stackoverflow.com/questions/56246948/how-to-tell-why-osx-code-signature-is-invalid Electron apps: macOS Hardened runtime, notarization, code signing: app crashes and doesn't work at all · Issue #3989 · electron-userlan… This leads me to believe that it's an issue which Apple have introduced in the way Notarization checks are done. If so, will they care enough about the Unity/AIR/Electron platforms to solve this before they release MacOS 10.15 Catalina?
... View more
‎Jul 22, 2019
03:20 AM
Sorry for the radio silence - have been away with my family and ignoring email. The bad news: I'm now getting that error on Mac OS X too for the notarized app: Exception Type: EXC_BAD_ACCESS (Code Signature Invalid) Exception Codes: 0x0000000000000032, 0x00001199ab481f30 Exception Note: EXC_CORPSE_NOTIFY The reason I hadn't picked this up before is because I was creating the notarized app on my new Mac Mini running 10.14.5 Mojave but then downloading and testing the install of the app on my older MacBook Pro 10.13.6 High Sierra (which I'm keeping behind an OS X version so I can still run Flash Builder 4.7). The notarised app installs and works perfectly on High Sierra and the crash only occurs on Mojave in my environment. DHL83​ - I wonder if that would be useful additional information for Apple Support? Have you heard back from them? [Apologies for not picking this up before - I was just so pleased to get the app installing before I went on vacation that I posted here without fully testing on Mojave.] This is a fairly critical issue for our business, so I'll continue working on it. Would love to hear from anyone who has ideas for further tests or can make progress with this.
... View more
‎Jul 13, 2019
12:48 AM
Have you tried cutting IntelliJ IDEA out of the process? You can compile from the command line using the AIR SDK. Other than that, I suggest Apple Developer Support.
... View more
‎Jul 12, 2019
01:34 PM
I presume you've tried those last steps varying the command line arguments to see if it works if you miss something out? Just checking also that the certificate you are using is the one that you got from Apple labelled 'Developer ID Application', not Apple Development, Mac Development or iOS Development. Also, do you have the latest version of Xcode installed? Other than that, I'm really not sure. However, since it sounds like an issue which is caused by Xcode signing with an Apple certificate, you should be able to contact Apple Developer technical support since you can prove the app runs before codesign alters it.
... View more
‎Jul 12, 2019
02:00 AM
Using AIR 32 and no further modifications to Info.plist. I'm also using Win10 on bootcamp on a MacBook Pro in my process. [As an aside, when signing on Windows, I first tried using one of the latest MacMinis but couldn't get the USB signing token to work under windows, which I'm guessing is down to the T2 chip in the MacMini. Signing tokens also don't work under virtualisation with VMWare Fusion or Parallels. Works fine on Win 10 running as bootcamp on an older MacBook Pro though. Not relevant to the Mac discussion but may be useful to someone who is using Bootcamp to run Windows to sign a captive runtime .exe AIR app.] Good luck!
... View more
‎Jul 12, 2019
01:38 AM
2 Upvotes
I'm not sure what's causing the error but I have two guesses: 1. My process is a little different to yours. I export an unsigned .airi from Flash Builder 4.7. I then (on Windows, though it shouldn't matter) use ADT to create an unsigned .air: adt -package -target bundle MyApp MyApp.air [I then sign that on Windows using Signtool but I think I use the unsigned version for Mac] Next, I move that .air file to Mac OS and create the .app (again, unsigned): adt -package -target bundle MyApp.app MyApp.air I then copy the .icns file into the package: cp -f MyApp.icns Contents/Resources/Icon.icns and finally run the script to remove Webkit and DRM and to sign the .app and its various components. 2. My second guess would be to check and double-check your certificates since that's what the error is stating. Also, have you followed the instructions in the Notarization link to get the full error message link when it fails? The full format of the certificate IDs should include the letters and numbers in brackets: e.g "Developer ID Application: Company Name, Inc (AB1CD2E3FG)" After completing all of the above, I create an installer .pkg file, signing that .pkg with my Developer ID Installer certificate from Apple (NOT the Developer ID Application one), which with xCode installed is: productbuild --component MyApp.app /Applications "MyApp.pkg" --sign "Developer ID Installer: My Company, Inc" --identifier "AppName" --version "1.0.0" That signed .pkg is what I submit to Apple for notarisation. Good luck - we're all just guessing here thanks to Adobe's lack of documentation about the details of publishing AIR apps to Macs in the various possible formats!
... View more
‎Jun 28, 2019
09:44 AM
2 Upvotes
Huge thanks to everyone for contributions to this thread and especially to ejthomas95746​ for providing the script. A few extra pointers for anyone doing this process: 1. As of AIR 31 or 32, there is an additional file to sign which is Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/A2712Enabler I'm not sure if it's necessary but it is easy enough to sign. 2. For future-proofing, Apple now likes all apps to be Notarized (and will require it for all apps from MacOS 10.15). Details of how to do it are here: https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution/customizing_the_notarization_workflow#3087734 For this to happen and for it not to fail, it's necessary to sign the A2712Enabler file and your MyApp.app file in a different way so that it includes a 'hardened runtime'. The updated codesign commands are codesign --force --options runtime --deep --sign "Developer ID Application: Your Company, Inc. (YOUR_TEAM_ID)" "./out/your-app.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/A2712Enabler"" codesign --force --options runtime --deep --sign "Developer ID Application: Your Company, Inc. (YOUR_TEAM_ID)" "./out/your-app.app" Notarization is then performed as per the document linked above. You have to create an App-specific password on your iTunes Connect account to do that. The document also contains details of how to find errors which is very important if the process fails. 3. Finally, you staple the notarization to the app, although there's no reference required, just this command: xcrun stapler staple "./packaging/mac/your-app.pkg" 4. One other note: It's quite acceptable to use the .air file built and signed on a Windows dev machine as the input to 'adt -package -target bundle' to create the MacOS Captive Runtime version (this saves us time in our build process). I also found the app 'iCreate icons' to be a really simple way to generate the .icns file required for Mac from the Windows png icons we already had. Hope this helps someone as much as everyone's previous answers helped me. Thanks all!
... View more
Copyright © 2024 Adobe. All rights reserved.
AdChoices