macOS Catalina 10.15. Any solution?

tuarua

Gene_Pavlovsky What is the icon building code for?

adt doesn't build a complete set of icons for the App Store. It is missing 512@2x which was added in recent years. A macOS Assets.car is also now expected. A notarized app maybe doesn't need these.

com.apple.security.app-sandbox is a requirement for App Store apps but not for Notarized apps.

To distribute a macOS app through the Mac App Store, you must enable the App Sandbox capability.

Given that you are running a Native Process (which is in effect the Terminal) you are operating outside the sandbox so you will need to disable it.
https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_app-sandbox

A Boolean value that indicates whether the app may use access control technology to contain damage to the system and user data if an app is compromised.

There's no secret magic to any of these entitlement settings. Read the descriptions to determine which ones you do/don't need to use.

https://developer.apple.com/documentation/security/app_sandbox
https://developer.apple.com/documentation/security/hardened_runtime

makanmel

hugo Hi Hugo, maybe you could help me with the captive runtime packaging issue ("Failed to load the AIR Runtime") asked here: https://forum.starling-framework.org/d/20802-adtair-developer-tool-is-what/26

hugo

Hi makanmel,

I use IntelliJ to do that for me.
After that, I have a script to extract the necessary to a zip file.
This zip it put in a specific location along in a xml version file to the update.

makanmel

hugo Thanks for the reply. I have updated to AIR 32 and my project started to package without issues.

StMulligan

@tuarua Late to the party, but just now trying to codesign my first Air captive bundle and living the nightmare of this thread. Seems your github script would have been a great help. Is it gone? Anyway I can get a copy? Thanks.

tuarua

@StMulligan
See https://github.com/tuarua/WebViewANE/tree/master/mac_installer

dhl83

Has anyone been able to sign on MacOS Big Sur? I'm getting:

MyApp.app/Contents/Frameworks/Adobe AIR.framework/Adobe AIR: bundle format is ambiguous (could be app or framework)

when trying to run

codesign -f -v -s "Developer ID Application: MyCompany (N99XXXXXXX)" MyApp.app/Contents/Frameworks/Adobe\ AIR.framework/

as one of the steps in the signing process, which worked before I upgraded to Big Sur...

I'm using this script by @tuarua, which worked perfectly in the past: https://github.com/tuarua/WebViewANE/blob/master/mac_installer/sign_developerId.sh

tuarua

I am not having any such problems.
Using Bug Sur 11.2.3 on Intel Xeon iMac
Tried both latest Harman AIR 33.1.1.444 and Adobe 32.0.0.116

Make sure your SDK/Adobe AIR.framework is not quarantined (run your app debug or unsigned .app first)

Something may have locked the file like an Antivirus or DropBox
https://forum.xojo.com/t/codesign-says-my-bundle-format-is-ambiguous/31893

Or your .app file is damaged, ie you are copying nested files into an older version
https://github.com/electron/electron-osx-sign/issues/181

dhl83

Symlinks seems to have been the problem. I wrote a quick summary of the steps I took to solve this for my app (AIR 32.0.0.116) compiled on Big Sur 11.2.3: https://github.com/Gamua/Adobe-Runtime-Support/discussions/716#discussioncomment-598762

Bilbosax

Tuarua, I successfully ran your mac_installer script to distribute an app outside of the App Store. No errors. I wanted to install the app for testing. When I install the signed and notarized installer package, it takes me through all the steps and successfully installs the app. But there is no app. Nothing in the LaunchPad or in the Application folder. Where did it go?? How can it successfully install something, but nothing be there?

tuarua

It is installing it over all original YourApp.app files ie the one that you used as the source.
macOS has an inbuilt quirk which means it does that.
You should test installing it on a machine other than the one you developed it on.

Jeff

tuarua

Haven't done this in a while but back when I was testing a signed Mac app .pkg before submitting it to the store, you could use the command line installer script (do man installer for all the documentation details).
It has a -target option which lets you choose where it installs the app...
so
sudo installer -store -pkg XXXXXXX.pkg -target /
would let me install it into /Applications, maybe this works with non-store distros too.

Bilbosax

Unreal. Another Apple loophole to jump through. As if their machine were not expensive enough, you need a second one just to test installing your app. I don't know if I even know somebody else who owns a Mac LOL

« Previous Page