User Profile

@eskimo - thank you so much for taking the time to give these details. We completely understand about the limits of what you can comment on and we appreciate that you have at least offered a glimmer of hope that there may be a way forward.So, based on your reply, here's what I've tried:1. I created an entitlements file using XCode: com.apple.security.cs.allow-jit 2. I referenced this entitlements file when signing the .app using codesign: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"3. I then used productbuild to create the .pkg:productbuild --component /Users/username/Documents/out/MyApp.app /Applications "/Users/username/Documents/out/MyApp.pkg" --sign "Developer ID Installer: My Company, Inc (AB1CD2E3FG)" --identifier “MyApp" --version "${VERSION}"4. I notarized the .pkg and then stapled it as detailed in the documentation.5. Finally did a fresh install on MacOS 10.14.5 Mojave and ran the app. I still get the crash with the same error.Update: For AIR apps, it runs without error if I assign both com.apple.security.cs.allow-jit and com.apple.security.cs.allow-unsigned-executable-memory So, now have a working notarized app. Hooray!@eskimo: Really appreciate your willingness to help us struggling developers to work out what the new notarization requirements look like in practice. Thanks!

@eskimo Thank you for the detailed analysis of the problem which is spot-on.We're getting exactly the same issue with apps compiled using Adobe AIR with captive runtime (not surprising since Actionscript has always been JIT compiled). The apps work perfectly and can be signed and notarized without any issues but when run on MacOS 10.14+ they crash with the same EXC_BAD_ACCESS (Code Signature Invalid) even though they have passed notarization. They run fine on MacOS prior to 10.14 and will work if the app is signed without the hardened runtime option and not notarized.There are others reporting the same issue over on the Adobe forums: https://forums.adobe.com/thread/1470113 (comments in the thread from July 2019 onwards)We really appreaciate that you've given a direct contact and have invited the developers of the compiler to talk to you - great support. However, the odds of a small independent software developer like us being able to get the code-level developer of Adobe's compiler to talk directly to you (or even to discover who they were and whether they're even still working on that project) are pretty low. What would you suggest we do? Our apps are mission critical to our business and notarization appears to remove the possibility of any Mac user running them successfully once it becomes mandatory in MacOS 10.15.Will Apple be providing a way for users to work-around this and install a non-Notarized app in MacOS 10.15 or will you be reaching out to Adobe directly? Without that, introducing notarization is gong to break every AIR app available for Macs, and kill off the Mac side of businesses that rely on them, which would seem quite drastic given that AIR is officially still supported on the MacOS platform. We love Apple and use Macs throughout our company and would be really sad to only be able to support Windows users!