Post

Replies

Boosts

Views

Activity

Reply to App modification after installation and MacOS security, code signing, app notarization
It would be easier to just bundle a copy of those libs inside each app. Then you won't need a .pkg to install them, or a deinstaller to remove them. Anyway, if the libraries you replace in your /Libraries/MyAppLibs/ folder are properly signed, there shouldn't be any issue. Each .app bundle or library outside an .app bundle is a separate entity. Changing one entity won't affect the others, just make sure you keep using the same signing identity. Changing something inside a .app bundle will break its signature, macOS doesn't check it every time, but the next time it will (and it will surely will) the app won't run anymore.
Topic: Code Signing SubTopic: General Tags:
Mar ’22
Reply to On building an universal binary on Xcode 12.3, why are the dynamic libraries under Example.app/Contents/Frameworks directory buillt for x86_64 archirecture only and not for arm64?
Swift ABI got stable in 10.14.4, this means that those libraries are now bundled with macOS. Probably you set the deployment target to a version older than 10.14.4, so Xcode bundles the Swift libraries, but only for Intel because the first macOS version for arm was 11, and it already includes those libraries.
Topic: App & System Services SubTopic: Core OS Tags:
Aug ’22
Reply to Xcode 14 and supporting macOS 10.9 - 10.12
Xcode ships only one SDK per platform. Xcode 14 still has the old macOS 12 SDK, while the beta had the macOS 13 SDK. This is because, just like last year and the year before, the new macOS version is still in beta, and Apple doesn't ship a beta SDK in a public release. The macOS 12 SDK allows to deploy to 10.9, the 13 SDK that was in the beta and that will be in Xcode 14.1 will allow only to deploy to 10.13 and higher.
Sep ’22