Author's Posts

If you’re using Yoink on macOS Sequoia, you might have encountered an issue where Yoink would not accept any files anymore:

Or if you’re using Transloader on macOS Sequoia, you might find your Link- and File Actions not working correctly:

Basically any app that handles file URLs and saves them as a security-scoped bookmark for later access can be bitten by this bug, currently occurring on macOS 15.0 and 15.0.1.

This is caused by a bug in the macOS daemon process called “ScopedBookmarkAgent”, according to a CoreOS engineer on macOS, as stated on the Apple Developer Forums:

What you’re hitting is bug in “ScopedBookmarksAgent” [sic] which can cause it hang if it happens to have been launched when the keychain was also locked (for example, late in the screen lock process). That bug is fixed as of macOS 15.1 beta 4.

– DTS Engineer, CoreOS/Hardware

The downside is that 3rd party developers like myself cannot fix this in their apps. Apple has to, in macOS.
The upside is that with macOS 15.1, the bug will reportedly be fixed and things should work as they used to.

As a temporary workaround, you can:
– Quit Yoink (or any other afflicted app)
– Using Activity Monitor.app, quit the ScopedBookmarkAgent process
– Relaunch Yoink (or any other afflicted app), and it should work again (for a while)

My apologies for the inconvenience. Here’s to hoping macOS 15.1 will be released soon.

Cheers,
– Matthias

Read more

For my screen-capture all-rounder app ScreenFloat, I’ve received feedback from users that, under macOS Sequoia, their keyboard shortcuts suddenly stopped working.

Well, with macOS 15 Sequoia comes an undocumented change that boggles the mind (and which developers have never been told about during the macOS upgrade’s beta period) :
In 3rd-Party-Apps, users are no longer allowed to set up keyboard shortcuts that use only the option ⌥, only the shift ⇧, or only option + shift ⌥ ⇧ keys as the modifier (like ⌥ ⇧ 2).

Why? As an Apple Frameworks engineer puts it, “to limit the ability of key-logging in malware”. A make–shift reason, if you ask me (or the other developers in that thread):

I also don’t get the logic. The change only impacts sandboxed apps, but malware wouldn’t use sandboxing. Plus, any app can request input monitoring and misuse it, so this mostly hurts legitimate apps and their users, and does very little to stop actual malware.
– sindresorhus

That’s sadly something that’s becoming more and more routine at Apple: punish developers that adhere to the sandbox and Mac App Store rules, for no good reason.

How does this even prevents key loggers?
– IzsakSVK

Beats me (and Apple).

Of course, as always, Apple’s own software is exempt from this restriction, as you can see in this screenshot of System Settings > Keyboard > Keyboard Shortcuts, where I could set it up just fine.
Why this matters? Consistency. Users expect that if it works in Apple’s software, it should also work in other apps they use. And I agree!

Just yet another change where Apple oversteps its bounds to prevent users from configuring and using their own computers how they want to.

Updated for macOS 15.2

Apple seems to have reversed their decision – option-based keyboard shortcuts are allowed again for sandboxed 3rd-party apps on macOS Sequoia 15.2.

Read more

macOS 15 Sequoia introduced a new, annoying screen capture permission reminder that has brought on a lot of push-back from developers (myself included).

Now, Ricci Adams has found a way to virtually stop the nagging for specific apps. (I found out about this from Jeff Johnson’s Desolation of Blog blog).

First things first: Please use your own discretion when trying this. Consider if you’re savvy enough to work with the Terminal, and if you really want to remove the permission reminder for an app.

Apparently, there is a TCC (Transparency, Consent and Control) – protected file that keeps track of when to show the next nag screen for specific screen capturing apps, located at

~/Library/Group Containers/group.com.apple.replayd/ScreenCaptureApprovals.plist

Using Terminal (which first needs to be granted Full Disk Access in System Settings > Privacy & Security), you can set that date far into the future so you won’t ever see the nag again.

For example, I wanted to make absolutely sure it never bothers me again for my own app ScreenFloat, so I just set it to my retirement date: January 1st, 4321.

defaults write ~/Library/Group\ Containers/group.com.apple.replayd/ScreenCaptureApprovals.plist "/Applications/ScreenFloat.app/Contents/MacOS/ScreenFloat/" -date "4321-01-01 00:00:00 +0000"

Restart your Mac (or log out and back in) so it accepts the new defaults, and you’re all set.

Read more