Hi, I'm PipThese Featured apps take turns in my notch.
iPipSubmit
Blog

Rosetta stops after macOS 27. Here is what I would check in my Mac app

By Justinas Rolando, maker of MacPip

Short answer

Apple says macOS 27 is the final release to support Rosetta, so Intel-only Mac apps stop running on Apple silicon Macs after it. From macOS 28, Apple says Rosetta stays only for certain older, unmaintained games. Since macOS 26.4, people have seen a notice when they open an app that relies on Rosetta, and macOS 27 lists those apps in System Settings. If your app is Intel-only, or ships an Intel-only helper or library, build it for Apple silicon now. Run lipo or file on the app and on everything inside it.

If someone opens your Mac app and sees a notice that it "will not work with a future release of macOS", that is Rosetta saying goodbye.

Apple has been clear about this for a while, and the date is getting close. Here is what it has said, and what I would check in a Mac app this week.

What Apple has said

Rosetta is the translation layer that lets Intel apps run on Apple silicon Macs. Apple's developer news post, Upcoming changes to Rosetta support for Intel-based macOS apps, sets out the timeline for makers:

Apple's support page, Using Intel-based apps on a Mac with Apple silicon, is a little more precise. It says Rosetta is available on Apple silicon Macs using macOS 27 or earlier, and that starting with macOS 28 it will work only for certain older, unmaintained games that rely on Intel-based frameworks. So the cut-off for ordinary apps is macOS 28, the next major release. Apple has not said when that ships, and I won't guess.

One more detail from this month. MacRumors reported on October 26 that Apple's enterprise release notes for macOS 27.2 say upgrading to macOS 27 no longer removes an existing Rosetta installation. So a Mac that had Rosetta before the upgrade can keep it, and the Intel apps keep running there for now.

What people see today

On macOS 27, there is a list. In System Settings, under General, then About, the macOS section has a Details button next to Intel-based Apps, and it shows the apps people recently used or that sit in common places. Apple's support page describes it. So a user can already see which of their apps are about to stop working, and whether yours is one of them.

If you use Activity Monitor, the Kind column shows Apple or Intel for each running process, which is a quick way to spot an Intel helper hiding behind an Apple silicon app.

What I would check in my Mac app

1. Is the app itself universal or arm64? Run lipo -archs on the main binary inside the app, in Contents/MacOS. If it says only x86_64, that's the whole problem. If it says arm64 or both, move on. The universal binary checker reads that output for you, right in the browser.

2. What about everything inside it? This is where apps get caught. A universal app can still ship an Intel-only helper tool, framework, plug-in, command-line binary or embedded runtime. Run file or lipo -archs on each one in Contents, including Frameworks, Helpers and XPCServices. One Intel-only piece can still bring up the notice.

3. Your dependencies. Old static libraries, prebuilt SDKs and bundled tools from other projects are the usual culprits. Ask the vendor for an arm64 build, or replace the dependency. A Python, Node or Electron bundle you ship needs to be the Apple silicon build too.

4. Your build settings. In Xcode, check which architectures your target builds for, and that your release build isn't pinned to Intel. Then build, notarize and test the arm64 version on a real Apple silicon Mac, not only under Rosetta.

5. Your website and your listing. Say what your app runs on, in plain words: "Apple silicon native". If you still sell an Intel-only version, say clearly that it will stop working on newer Macs, and tell the people who have it.

If you just use a Mac

Open the Intel-based Apps list in System Settings. For each app on it, check whether the maker has an Apple silicon update, and write to them if you can't tell. It costs a minute now, and it is far nicer than finding out when an app refuses to open on a new Mac.

The MacPip angle

Whether an app runs natively on Apple silicon is one of the first things people want to know, so it belongs on a listing. If you're getting your app ready, the get ready for the next macOS prompt walks a coding agent through the checks above. And listing it on MacPip is free. Listings are scanned automatically when they're submitted, and a blue tick only means MacPip checked the app on a date.

Sources

Keep reading

Making apps for iPhone and iPad too? They have their own free home on iPip, MacPip's sister directory.

Submit your appFree tools for makers