Macos – Old(ish) application doesn’t work in macOS Sierra

macos

I recently downloaded the Public Beta of macOS Sierra, and everything is working perfectly – except that one application won't launch. macOS draws a large banned / not allowed sign through the icon (see image), and when clicked displays a dialog saying:

You can’t use this version of the application “Fraise.app” with this version of macOS.

This is interesting as it was not a PowerPC application – I have upgraded from El Captain (where the application worked fine), not some ancient system such as Mac OS X Leopard.

I can't seem to find any information online about such a problem, nor can I understand why it is occurring. OS updates normally do not stop previously working apps from running unless there is a very significant change in architecture – which there is not as far as I'm aware.

So, my question is: why is this happening, and is there anything that I can do to get the app running again?

Also, I know it is beta software, and that there are all sorts of bugs / problems / risks involved in running it, which could explain this. The application is not vital to my workflow, nor am I using my main computer to run the beta. I am more just interested in why this is happening then if there is a fix.

Best Answer

Choose “Show Package Contents” in the context menu.
run Contents/MacOS/Fraise

I assume that the error will be "Objective-C garbage collection is no longer supported.". It seems that Apple is no more supporting those old apps with "garbage collection with macOS 10.12.

Delete my answer if you don't like it and don't ask why I won't post anymore.

Related Solutions

Linux – rEFInd not working on macOs Sierra: “Not found while loading legacy loader”

The error message you're seeing indicates that you're attempting to boot a disk in BIOS/CSM/legacy mode and it's not working. This is a common problem on Macs when booting USB drives, and unfortunately, the causes are many and such problems can crop up on some specific Mac models but not on others, which makes these problems very difficult to debug and fix. Worse, the way that rEFIt (and therefore rEFInd) boots in BIOS mode on Macs is very cryptic, so it's hard for me (I'm rEFInd's maintainer) to support this code. In some cases, holding down Option (or Alt) as you power on the computer will work better than rEFInd for booting a USB drive in BIOS mode, so you might try that.

It's usually better to boot USB media in EFI mode, if at all possible. Unfortunately, some tools don't create EFI-bootable USB drives, so you may need to try several tools before you find one that works. In theory, both Rufus (Windows only) and dd (Linux and OS X) should work, but Rufus has several options that you must pick correctly, and dd can easily be used incorrectly. See here for some more on this subject.

Another alternative, if your Mac has an optical drive, is to create a DVD from the .iso file. Your recent MacBook probably lacks this feature, but an external optical drive might work, and so is worth trying if you have access to one.

Macos – mDNSResponder on macOS Sierra? Malware

The mDNSResponder service is associated with Bonjour, a network browsing service that auto-browses the network for resources. For example, it knows at all times about network printers and its list is up to date. That is what Bonjour does : It polls the local network segment and discovers devices that you can connect to.

The mDNSResponder service is the engine of Bonjour. Sometimes it can go a little crazy and there are enough articles on the web complaining about it.

There are two launch daemons that manage the Bonjour service. If they are unloaded, Bonjour will shut down and the mDNSResponder activity will stop.

The following commands might still do the job in OS X Sierra :

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponderHelper.plist

Unfortunately, per your report, shutting down mDNSResponder also left you without Internet access. Well, at least this turned out to be the confirmation you asked for that this is a legitimate OS X process.

Since Bonjour is a network-browsing process, its presence on the one Mac but not on the other may be explained by some difference in the network. For example, it might be checking that a network printer is still available.

Related Question