In just three days last week, Apple released nine major products which demanded the attention of independent developers. How did that work out, then?
Stepping through building it correctly in Xcode, turning it into an Installer package getting it notarized and the ticket stapled to the tool.
Coming now to Apple Silicon Macs: all ARM-native executable code is required to be signed. Full details of this important change.
Pages refuses to open the document. So how can you gain access to its previous versions?
If you’re running an interpreted/JIT language, Big Sur could return that it’s either 10.16 or 11.0, depending on the version of the environment.
macOS 11.0 will identify itself differently according to the SDK used, and an environment variable does the same for scripts.
How does Big Sur convince older software that it’s macOS 10.16, but to newly-built app it’s macOS 11.0?
Both apps now detect and report apps which have been built using the 11.0 SDK, and ArchiChect reports non-Intel architectures too.
Will they be locked down completely, or run iPadOS? How could they run existing Mac apps? Some potential answers.
In a public recruitment advert, Apple has effectively announced that it’s developing new cloud-based services for third-party developers. […]