Om Malik (2023):

One of the key advantages of MacWhisper, as it utilizes the Whisper technology, is its superior accuracy in transcriptions compared to other services I have used. I was an early adopter of Rev.com and eventually switched to Otter.ai, for which I paid approximately $100/year. However, I have since canceled my subscription.

[…]

After comparing the audio transcripts from MacWhisper and Otter, I found that while Otter’s formatting is superior, there is hardly any difference in the transcriptions. I started with the free model, which was sufficient for my needs, and eventually upgraded to the large models. Nowadays, I primarily use MacWhisper to transcribe my voice memos, which I then import into Lex.Page.

Bon Adamson:

Whisper, which is made by OpenAI, has the distinct advantage of allowing you to transcribe audio in almost any language you may ever need to. For the time being, Otter can only transcribe English. The benefits of better accuracy and accurate punctuation that the service already holds over Siri hold up across other languages as well. If you’re looking to transcribe non-English audio accurately, Whisper is definitely the best option available on Mac.

Dan Moren:

By taking advantage of OpenAI’s Whisper framework, Audio Hijack can now take any audio it’s recording and generate a text transcript. While this process was possible before—see Jason’s lengthy post about his workflow—it required a lot of fiddling and several different tools to accomplish; it’s certainly a lot easier to simply drop Audio Hijack’s block into your existing session. If you record multiple sources, it can even appropriately label each one—though if you record multiple people via one input, say the other end of a Zoom call, it can’t distinguish between the various participants.

Inscribe (2026, Hacker News):

Apple’s new SpeechAnalyzer is the most accurate on-device speech engine we tested. It beat every Whisper model we ship, including Whisper Small, on both the clean and the noisy half of LibriSpeech, while running roughly three times faster than Small. And the API it replaces, SFSpeechRecognizer, came last on clean speech: behind even Whisper Tiny, a 40MB model.

[…]

The new API cuts word error rate by 3.5 to 4x on the same audio: from 9.02% to 2.12% on clean speech, and from 16.25% to 4.56% on noisy speech. There is no accuracy trade-off to weigh; the new API wins everywhere we measured, and it produces punctuated, cased text where the legacy engine’s output is rougher.

[…]

All five engines ran comfortably faster than real time: between roughly 12x and 40x on the M2 Pro, meaning an hour of audio transcribes in about 1.5 to 5 minutes on-device. SpeechAnalyzer was about 3x faster than Whisper Small per second of audio while beating it on accuracy.

Yuki:

SpeechAnalyzer’s ReportingOption.fastResults reads like a knob you’d reach for when you want to trade power for latency. That framing is what cost me the afternoon.

[…]

If a recording matters — and in a notes app, a lost meeting is the worst thing that can happen to a user — then the container you write while recording has to be PCM in CAF. Not m4a, and not AAC-in-CAF either.

[…]

AVAudioEngine’s inputNode silently ignores your device selection

[…]

I wanted summarization to run on-device. Everything else in Nib’s transcription path does, the audio never leaves the machine, and it would have been a much cleaner story to tell.

But 4,096 tokens for the Foundation Models isn’t enough.

Previously:

• Apple Foundation Models in appleOS 27
• WhisperPad Rejected From the Mac App Store
• Overcast Transcripts
• Generated Transcripts in Pocket Casts
• Apple Podcasts Transcripts
• Dictation and Predictive Text in macOS Sonoma and iOS 17
• macOS vs. Dragon Dictation

Thijs Xhaflaire (via Ric Ford):

Jamf Threat Labs discovers and investigates CrashStealer, a C++ macOS infostealer that impersonates Apple's crash-reporting framework to harvest browser credentials, cryptocurrency wallets and keychain data, encrypting stolen files with AES-GCM before exfiltrating them to a remote command-and-control server.

[…]

Unlike the payload it eventually installs, the dropper is properly code signed and notarized: it is a universal (arm64 and x86_64) binary signed with the Developer ID Emil Grigorov (WWB7JA7AQV), has hardened runtime enabled, and carries a stapled notarization ticket. Notably, the disk image itself is signed as well, not just the application inside it, which is uncommon in malicious DMG delivery where the container is typically left unsigned.

[…]

That file supplies the curl command the dropper runs next. Staging the first hop on a trusted developer domain keeps the initial network activity inconspicuous.

[…]

[The script] clears extended attributes on the staged bundle with xattr -cr, makes the inner binary executable, strips the payload's existing signature and re-signs it ad-hoc (codesign --remove-signature followed by codesign -s - --force --deep --no-strict), registers it with Launch Services via lsregister -f, and finally launches it in the background with open -g -n.

Previously:

• Notarized Mac App That Downloads Malware
• Fake Mac Apps on GitHub
• Notarized Atomic Stealer (AMOS)
• More Notarized Mac Malware
• App Transport Security

Aleem Shaun:

I’ve used Day One for more than a decade. It was an excellent journalling app. Private, minimal, easy to use, with excellent features such as geolocation, weather, ‘On this Day’, and book printing. Features that got out of the way and either worked quietly in the background or appeared only when you summoned them. That’s changed.

Now there are new subscription tiers. Previously, the tiers were Free and Premium. Simple. Premium included sync and a few other things that I can’t remember, but it was compelling enough that I’ve been a Premium subscriber from the beginning. Now, without consultation, I’m Silver (not Premium), and there’s a new, more expensive AI-driven tier, Gold. I don’t object solely on that basis. You would think I could just choose to remain on ‘Silver’ and all would be well. But no. Even with these features turned off in settings, I’m visually prompted in the app to upgrade to Gold and use the Daily Chat (with AI), which I’ve turned off and can only use if I upgrade. And yet, there it is, taunting me.

Via Eric Schwarz:

Even Apple is guilty of doing this in the Settings app and the former iWork apps.

Previously:

• $10 Off at Fandango
• Automattic Acquires Day One
• Productivity Apps and Subscription Pricing

John Gruber (Mastodon, 2):

Some of [Cook’s letter] remains true, but has lost some truthiness — and truthiness matters. But some of it is no longer true, period. It’s no longer just “one small part” of Apple’s business that serves advertisers. Here in 2026, search results in the App Store not only show paid ads — frequently for casinos — but the search results are visually dominated by paid ads now that Apple has added a second ad to results. Apple News+ is a paid subscription that offers a genuinely great value for the number of paywalled publishers whose content it includes, but articles on the News app tend to include the weirdest AI-generated ads on the Internet. (How many young blond women am I supposed to believe need hearing aids?) And — at this writing, still “coming soon” — Apple is launching ads on Apple Maps. Apple Maps remains free of charge to use, so according to Tim Cook, we’re not the customer. We’re the product. Or, if you prefer, our frustration is the product.

[…]

The ratio of ads to organic results in App Store search — especially when measured in screen area — is clearly not aligned with Cook’s 2014 statement that “Our software and services are designed to make our devices better. Plain and simple.” Obviously not. App Store search today is designed primarily to generate more revenue for Apple. That’s not criminal, but it’s a change.

[…]

What gave Tim Cook’s privacy letter heft in 2014 wasn’t just the clarity of its plain language, but the fact that you didn’t have to take his word for it that the ads Apple showed you respected your privacy, because Apple didn’t show you ads in 2014. Apple today can’t say that.

[…]

John Ternus should return Apple’s privacy policy to its 2014 clarity. The trust Apple would earn from such a move would far out-value whatever revenue these ads pad to their already hefty and ever-increasing quarterly Services numbers.

I wish that were the case, but I fear this is kind of a Hotelling’s Law situation, where Apple can get most of the benefit by being just slightly better on this axis. Where else do its customers have to go?

Jeff Johnson (Mastodon):

In the second fiscal quarter of 2018, services generated $9 billion in revenue (net sales), whereas in Q2 2026, that amount had grown to $31 billion! In this blog post, I want to focus on understanding the relative financial importance of products and services for Apple.

[…]

In 2025, services were 42% of Apple gross margin. How does 26% of net sales become 42% of gross margin? The explanation is that services have a much lower cost of sales. The products gross margin was 37% of products net sales, while the services gross margin was an astonishing 75% of services net sales. In other words, Apple services are almost pure profit!

Does this 75% account for TV and movie production costs?

With persistent general inflation, consumers do not have unlimited money to spend on Apple products. At least in the near future, it’s reasonable to question how much further room is available for growth in profits from Apple products. To satisfy the demands of investors, Apple executives including CEO-elect John Ternus may be forced to rely even more than before on growth in services, which do not face as much pressure on cost of sales as hardware products.

Previously:

• Apple Services Price Hikes 2026
• Apple Hardware Price Hikes
• App Store Personalized Recommendations and Keylogging
• Apple’s Q2 2026 Results
• A Letter to John Ternus
• Ads in Apple Maps
• Blurring App Store Ads and Search Results
• Apple Services in 2025
• More App Store Ad Spots
• Apple Services Price Hikes
• Nowhere Else to Go

Jared Sorge:

I know there are options out there like Paddle, FastSpring, and Lemon Squeezy that have worked for many apps like mine over the years. But I also wanted something simple for my users. Not to mention Apple Pay was a must-have.

I believe all the services he mentions do support Apple Pay.

• RevenueCat serves as the source of truth for whether or not a customer is licensed.

• I create RevenueCat customer IDs from local iCloud identifiers (more specifically, calling userRecordID() on my CKContainer in CloudKit).

• When the user makes a purchase, they earn an entitlement that I look for in Arborist to grant them a license.

He doesn’t need to run his own server, and the purchases are automatically tied to the user’s iCloud account, so there are no e-mails or serial numbers to deal with. On the other hand, well, it’s all dependent on the Apple Account.

The app, which helps manage Git worktrees, is shipping now.

Previously:

• Locked Out of Apple Account Due to Gift Card

Bruno Brito (release notes):

In Tower 15, we introduced the “Fully Merged” badge and Automatic Branch Management to help you keep your repository tidy. With Tower 17, we’re taking the detection behind that badge to a whole new level. […] Tower now matches your local branches against merged pull requests from your hosting service, such as GitHub or GitLab.

[…]

Trust is everything when deleting branches — so we redesigned the “Fully Merged” hint view to show you exactly which checks matched.

[…]

One that is particularly noteworthy is that updating submodules is now significantly faster! Tower gathers each submodule's Git data concurrently instead of one at a time—something you will especially notice in repositories with many submodules.

I’m sad that they got rid of the yellow icon.

Previously:

• Git Tower 16

Federico Viticci (Mastodon):

The AI frontier from the two big labs (and – we have to be honest with the numbers here – probably SpaceXAI and Meta now, too) is in a completely different league at the moment. I spent my first couple of weeks with Siri AI trying to convince myself that I could replace Codex with Siri AI, and that was the wrong approach. There is a potential future in which Siri AI can become a more proactive and capable agent, but that’s not what Apple is shipping this year.

[…]

Siri AI is a dramatically better Siri for typical Siri stuff. The new Siri understands your commands and nuanced requests better because of the LLMs behind it; it can often perform multiple requests in one go (such as setting multiple timers with one command); the new expressive (and customizable!) voices sound great, and they’re terrific at reading and summarizing notifications. Apple’s first advantage compared to other chatbots is right here: only Siri can integrate with the iPhone and iPad to this extent, so even if the Foundation models aren’t as smart as the competition, Siri can do a lot more for most people on their devices because neither OpenAI nor Anthropic have OSes they can control.

[…]

The biggest issue I’ve encountered is the inconsistency of it all. Very often, the new Siri AI still replies with a generic “Uh oh, something went wrong“ error that doesn’t explain what the error was or why it happened. Sometimes, I ask a question via voice, and it errors out, but then a few seconds later, I type the same question in the app, and it’s fine.

[…]

My problem is that, right now with Apple’s own apps, both the index and Siri’s ability to perform actions are very inconsistent. The assistant hallucinates abilities it doesn’t have, and it frequently just doesn’t work.

Dan Moren:

The good news is that Siri AI is capable: impressively so, at times. In the lowest of low bars, it certainly beats the pants off the previous incarnation of Siri, but its access to your own personal data and all of the app on your phone also unlocks a host of new possibilities.

But it’s also not without the pitfalls that underlie all LLM-powered chatbots: errors in understanding, hallucinations, and so on.

[…]

The app itself is pretty barebones, letting you view those conversations in List or Grid layouts, select multiple conversations to delete them, and pin or rename any single conversation. In Settings : Siri, you can choose to either open to the overview or to a new conversation and decide whether old conversations are kept for 30 days, 1 year, or forever. It’s a little strange that one-off queries (“What’s the average height of the Norwegian World Cup team?”) are stored alongside more involved conversations (“Can you help me build a specific RSS feed for this site?”); I also ended up with a few orphan blank “New conversations” which I deleted, but it’d be nice if you could filter to find those. Conversations are fully searchable and sync between devices via iCloud.

John Voorhees:

Despite the current limitations, if you use chatbots as a replacement for Google Search, you’ll probably have a good experience with the new Siri app. That’s because even in these early betas, if you ask Siri something like, “Give me a day trip itinerary for a trip to Chicago this Saturday,” you’re likely to get good but pretty middle-of-the-road recommendations. From there, though, you can drill down with follow-up queries to get something more in line with your tastes. The results include source links you can follow, too. Given the ad-strewn mess that web search has become, using Siri for this sort of thing is a meaningfully better experience.

The one caveat on Siri’s world knowledge is that it’s roughly 2-3 weeks stale in some places.

[…]

A good example is Music. You can prompt Siri to play a song, but most of the rich metadata in the app isn’t exposed to Siri, which is a shame because it is exposed elsewhere, for example to AppleScript.

Previously:

• macOS 27 Public Beta
• iOS 27 Public Beta
• No Siri AI in EU
• Siri AI Announced

Update (2026-08-04): Benjamin Mayo:

Thanks to the top-to-bottom revamp that is Siri AI, Siri is reliably intelligent. Finally. We are still in the midst of beta season, and Apple is yet to confirm whether Siri AI will formally launch with iOS 27 in September or sometime later in the year, but the feature is up to scratch. There are bugs and glitches and edge-case quirks, but on the whole, it wipes the floor with old Siri and is competent enough to supplant my everyday usage of other chatbots too.

[…]

Siri AI can get a snapshot of what’s on screen, but it cannot control the UI for you autonomously. As such, if you ask it to do something outside of its library of available app actions, it will say it can’t do that. Often, it can quote the relevant steps for you to do it yourself, but obviously that falls short of the ideal experience. This feels a bit lacklustre to people already embracing AI agents en masse. Claude and Codex on Mac do not hit these walls; they are all too keen to move your mouse for you and run terminal commands until the job is done.

Previously:

• ChatGPT Work and ChatGPT Classic
• Claude Desktop App
• Perplexity Personal Computer
• Codex for Almost Everything

Wade Tregaskis:

In short: if you have any file in your app (or whatever it is you’re trying to get Apple to sign) that is over 4 GiB, you must use a disk image (DMG) to package it for notarytool, not a zip file.

This is because support for files larger than 4 GiB requires using the “Zip64” zip file format, which would be fine except Apple’s notary servers can’t handle them.

Previously:

• altool Update and notarytool

Update (2026-07-22): Rosyna Keller:

It’s recommended to notarized exactly what you’re going to ship to users and shipping zips is extremely risky because you never know what tool the user will use to decompress the file.

Multiple unzipping tools will strip necessary extended attributes that could cause the code signature to fail to validate. This is especially true if you put non-code files in “code places” and they have to be signed with an extended attribute.

Paul Kafasis:

With last year’s release of MacOS 26 (Tahoe), Apple made a mess of app icons. In the first betas of MacOS 27 (Golden Gate), however, there are signs of a turnaround. We’re urging Apple to continue making improvements, by restoring the ability for MacOS app icons to have distinct shapes.

[…]

After decades of beautiful, memorable Mac icons in varying shapes, Tahoe flattened personality to obtain bland uniformity. The platform is worse for it.

Past icons weren’t just more expressive. They were also more usable. Having distinct shapes provided a useful way to tell icons apart. Tahoe eliminates that cue by forcing everything into the same squircle, leaving color as the primary way to tell icons apart at a glance.

Jason Snell:

Kafasis makes the important point that uniform shapes make it more difficult for users, especially those with vision issues including color deficiency, to differentiate between icons.

John Siracusa:

Squircle Jail is the worst design-related thing Apple has ever done to Mac developers, and probably the worst icon-related thing it has ever done, period. Incredibly developer-hostile.

If squircled icons are actually better, then let that design win in the market. That’s how we transitioned from the classic Mac OS icon style to the more photorealistic Mac OS X icon style. Developers adopted it because they wanted to, and because users desired it.

John Gruber (Mastodon):

The squircles, I will point out, are not in and of themselves the problem. The problem would be the same with any mandated shape, like, e.g., VisionOS’s circles.

[…]

I can’t think of any other design crime Apple has ever foisted on Mac developers that I’d argue (with Siracusa) was worse.

[…]

It’s like Apple decided every single one of its own apps must wear a stupid-looking hat, and they put those stupid-looking hats on third-party apps too, whether the developers of those apps want them or not. Scratch that. Not hats but helmets.

[…]

Just the mere silhouette of the old Keynote icon is more recognizable, and thus more iconic, than any icon on any platform from Apple today.

Jeff Johnson:

The traffic sign analogy hits me personally, because the StopTheMadness icon used to be shaped like a stop sign, but I was practically forced into making it a generic road sign.

Gus Mueller:

I get why Apple did it, but I think it’s completely wrong for the Mac.

Marcin Wichary:

On his blog, Jim Nielsen writes how Apple filed away so much expression by forcing rigid icon bureaucracy in macOS. Nielsen focuses mostly on distinctiveness; previously, you could make the icon unique by its general shape or the shape of its contents, but one of these two levers has now been taken away[…]

[…]

However, one also can’t help but notice how ugly and amateurish the Creator Studio icons are, so it all feels absolutely like a net negative – the new system took something away and the proposed replacement feels low quality[…]

Rui Carmo:

I, too, find the squircles aesthetically offensive and utterly pointless.

[…]

The part that genuinely breaks my brain, though, is that I now find icons on Linux more distinctive than on macOS, which would be impossible for my ten-year-ago self to believe. The platform that built its reputation on craft and visual identity has spent a year sanding it off, while the one everyone used to mock for its inconsistency is where individuality survives.

Jeff Johnson:

The subliminal, Orwellian message of the squircle jail is that all software is subservient to Apple, merely accessories to Apple devices, interchangeable cogs in the machine.

Mario Guzmán:

Had to grab the rest of the icons from #MacOSX Leopard. Gosh, they’re so, so pretty. So finely crafted. Gorgeous. Love it.

Dr. Drang:

I agree, but Apple’s 50th anniversary has gotten me thinking a lot lately about the early days of the Mac, so it’s only natural that my mind shifted to the highly constrained icons Mac applications had back then.

[…]

Many of the complaints about squircle jail are about the loss of icon elements that “stick out” from the rest of the design. As you can see, this idea was there from the very start; the hands stick out from the tilted rectangles.

John Gruber:

I never loved the hand on these icons. It felt too uniform. It functioned like a “this is an application” badge, but such a badge never felt necessary to me.

[…]

I think it’s less that Apple gave up on them and more that it came into focus that the “hand holding a pen over a diamond-shaped document” convention was intended for document-based apps. It signified “This is a creative tool that you use to create documents”. Apps that weren’t about creating document files — like Disk First Aid and Font/DA Mover — got different icons. Font/DA Mover’s truck icon in System 2 signified that you use this tool to move things. Disk First Aid’s ambulance was an obvious metaphor for repairing something unwell.

[…]

But the main thing about the “hand holding pen over diamond” convention was that it was only ever a convention.

John Gruber (Mastodon):

(a) I don’t think this is a good mandate for iOS either;

(b) it was always so for iOS, though, so it’s not like Apple has ever taken away rich creative icon shapes on the platform;

(c) MacOS is a far richer and more precise environment than iOS.

[…]

App icons on the iOS home screen are effectively simple buttons. I think it’s rather obvious that’s why they have had that squircle/roundsquare shape ever since the iPhone was announced in January 2007 (source). They’re one-tap launchers. App icons in MacOS are not mere buttons. You can drag them, move them, and drop things on them. You click them to select, and double-click to launch. They are richer objects that deserve a richer visual vocabulary. iOS is a world meant for fat-tipped Magic Markers and blunt safety scissors. MacOS is a world meant to support fine-tipped drafting pens and precision razor-sharp X-ACTO knives.

Louie Mantia (Mastodon):

While developers have submitted full-bleed square images for iOS app icons since 2008, for these new squircle icons in macOS 11, Apple provided a template to compose app icons in an image editing tool like Photoshop, with full control over the canvas beyond the suggested—but not required—squircle. This template made it easy-ish for designers to compose macOS app icons that were identical to or synonymous with an iOS app icon, while leaving the door open to continue using arbitrarily-shaped app icons on macOS.

[…]

The second type of Squircle Jail is more controversial, because these app icons were specifically drawn with the intention of fitting in. Overriding that intention feels like punishment for having done the right thing. App icons in a style that was recently encouraged by the system are now scaled down and put inside the squircle as if it were a container. Every icon that was utilizing the previous squircle shape suddenly looks much worse than before.

[…]

Instead of taking care to design and develop solutions specifically for Mac and iPhone, newer and bigger companies that don’t only make apps often ship apps with logo icons, rather than app icons. We’ve all seen it.

[…]

I would love if Apple provided a way for designers to poke outside that squircle boundary. Some of my favorite app icons did that. But also some of my least-favorite app icons ignored this shape entirely, when it was used for every system icon in the last five years. Whenever those apps showed up in my Dock, it was like a stain on my shirt I couldn’t get out.

John Gruber:

Ultimately this is what I object to with the squircle mandate. It favors the bottom of the heap by restricting the top. It makes bad icons mediocre but pushes great icons toward mediocrity too. That’s not The Macintosh Way.

Nick Heer:

Mantia touches on all the pragmatic reasons to unify the shape of icons in an operating system, all of which I have considered, and then drops the above paragraphs — and things started to make more sense to me. This is a different way to think about it. This is not a situation where a cleaner looks like a zesty beverage with toxic consequences. The shared general function of these icons does help communicate something and makes them less ambiguous in that sense.

But a broad category of functionality is only part of the story of an icon and — with respect to Mantia’s long and illustrious history of work in this area, and that of co-Parakeeter Luka Grafera — taking away a difference of shape also limits what an icon can communicate. It may not be a cleaning product that looks and is packaged like juice, but imagine if every consumable liquid was in identical bottles with only a different label.

Steve Troughton-Smith:

Louie’s squircle jail post just underscores that the squircle jail benefits 99% of apps, and is better for the platform overall. There is only ever a handful of apps that make great Mac app icons, and a withering number of ‘great Mac app icon designers’ — you can probably only name one or two left in the scene.

Jeff Johnson:

Mantia talks as if it were more important for apps to “belong to the Dock” than to allow Dock users to quickly select the right app in the list. That’s choosing form over functionality.

“The shape of apps is a squircle.” But Mac users already knew those were apps in the Dock!

See also: Accidental Tech Podcast.

Tyler Hall:

If you’re lucky enough to distribute an app outside the Mac App Store, you can break free of squircle jail using NSDockTilePlugIn. It’s not strictly the intended use-case of that API. And it’s not allowed in the Mac App Store, either. But it can solve the problem.

BasicAppleGuy:

If you recognize these icons, it’s probably time to schedule your routine back exam.

Previously:

• Clear and Tinted Icons Are a Hard Pass
• Liquid Glass 27 Icons
• Apple Creator Studio Icons
• Tahoe’s Terrible Icons
• One Size Does Not Fit All
• macOS Tahoe 26 Developer Beta 4
• macOS Tahoe’s New Theming System
• macOS Tahoe 26 Announced
• The macOS App Icon Book

Update (2026-07-17): Louie Mantia:

But my perspective right now is to be very pragmatic. The decision to mask all icons with squircles is a long-time coming. It was perhaps the most predictable thing to happen in Apple’s history. For 20 years, it’s been leading up to this.

I want to make nice things for macOS, whatever macOS is. And this is what it is.

Roger Wong:

Some of my favorite icons over the years have had interesting shapes, like the truck for Transmit, the vise for Compressor, or the cute bird for Twitteriffic.

[…]

But I also recall clicking some icons and not being able to select them. Why? Because I was inaccurate in my click and instead my cursor landed in the empty space just outside the shape.

[…]

If I recall correctly, developers could use a different mask for the click target to help users out. But I don’t think many did all the time, including Apple, which you can obviously see in the video above.

Louie Mantia:

I don’t want to step on toes regarding your new [StopTheMadness] icon which has great color— but I don’t understand why you elected to abandon the octagon as the outer shape. That’s a choice. You are not forced to abandon it. Why not do something like this?

I like this.

Nick Heer:

Losing some of the artistry in an icon makes it more difficult to distinguish between legitimate and well-crafted Mac apps, and everything else. It is not a perfect proxy, to be sure, and there are some very nice squircle icons. But it is nevertheless a unfortunate change that makes apps of varying levels of quality look more similar.

Adam Engst:

Of the TidBITS readers who chose to respond to the poll, only 1% said they use clear icons on the Mac, and no one admitted to using tinted icons. On the iPhone, clear icons were twice as popular—a whopping 2%—and just 1% of respondents said they use tinted icons. Dark icons, which retain color, were slightly more popular, but still couldn’t exceed single digits, with 6% on the Mac and 9% on the iPhone.

Squircle Jail is one thing; redesigning icons to be assembled within Icon Composer is another. The latter makes a lot less sense but for supporting clear and tinted icons.

Previously:

• Golden Gate Squircle Jail
• Icon Composer Notes
• macOS Tahoe’s New Theming System

SpamSieve 3.3.1 is an update of my Mac e-mail spam filter that improves the filtering accuracy and includes various optimizations, fixes, and updates for macOS 27. Some interesting engineering issues were:

• I’m still supporting macOS 10.13, but the app can now build with the macOS 12 deployment target in preparation for Xcode 27. The way Swift handles calling deprecated APIs remains annoying. You need workarounds like protocols to suppress a warning in a particular region of code. Often, I am updating to a newer API, but I want to continue using the old one on earlier versions of macOS. Right now I am heavily testing on macOS 26, so I would like to only deploy the new code there. Sometimes the initial versions of APIs are buggy, and I don’t want to have to retest every feature on every version. But Swift doesn’t like me to gate the calls to macOS 26 and later if the new API was actually introduced in, say, macOS 11.

• The most risky update was probably switching to the Swift API for Scanner. This is tricky because the current scan position changes from being based on UTF-16 indexes to String.Index. And in some cases my code was intentionally scanning into the middle of a combining character. I was really glad to have extensive tests here.

• Recent versions of Tahoe introduced a Core Data bug that broke save recovery (when invalid Unicode can’t be written to the database and we have to fix it up first). When the error comes in, SpamSieve looks under the NSDetailedErrorsKey key, but the value of this key is "NSDetailedErrorsKey" while the actual error info is under the key "NSDetailedErrors".

• Database corruption combined with a Core Data bug and two Swift behaviors were causing crashes. The root problem, I think, is that in this situation Core Data neglects to set the error pointer for -[NSManagedObjectContext countForFetchRequest:error:]. Normally, Swift would detect this and throw a generic nilError. However, this method signals errors by returning NSNotFound instead of nil. It’s annotated as swift_error(nonnull_error), which I think means that Swift doesn’t even look at the return value, only the (unset) error. So my code was receiving NSNotFound on the non-error path, treating it as a real count, and doing some math with it, which (by default in Swift) leads to a crash if there’s overflow. Now my code checks for NSNotFound and uses Int.addingReportingOverflow().

• I reimplemented Core Data batch fetching because of two problems with the fetchBatchSize option. First, it logs spurious errors when fetching from multiple stores at once. Second, it leads to high memory use. It will load objects in batches, but it never releases the earlier batches. You can manually refault objects that you no longer need, but it will still hold onto the full object shells, which can add up. My implementation only holds onto IDs, and it can fetch the IDs using a different context than the objects to push more work to background threads.

• I’m now using String.makeContiguousUTF8() in various places to avoid slow iteration of bridged strings.

• There was a regression where some menu code could crash on macOS 10.13. -[NSMenu setItemArray:] is only available on macOS 10.14 and later, whereas the getter is always available. With old Objective-C, the two methods could be annotated with separate availabilities. The Objective-C property syntax doesn’t allow this, so there’s no way for the compiler to flag calls where the setter is missing.

• The AppleScript support works much better with large data sets. The key, I think, is to never return an array to Cocoa for a scripting property/element. First, if you give it a lazy array it will sometimes try to access all the elements even if it only needs a few. And, second, AppleScript will run out of memory if the array is too large. By using indexed accessors, you can maintain laziness and only convert one object to a descriptor at a time. By caching a batch-fetching collection, you can limit the number of fetches and respond quickly when AppleScript requests individual objects.

Previously:

• Xcode 27 Announced
• SpamSieve 3.3
• Swift Proposal: Precise Control Flags Over Compiler Warnings
• Swift at 10

Juli Clover:

Apple today released the first public beta of macOS Golden Gate, expanding the macOS 27 beta test to non-developers. You can sign up to test the update on Apple’s beta website, and then download it by going to System Settings > General > Software Update and toggling on the macOS 27 beta.

Jason Snell:

The fact that there are more design changes in macOS than any of Apple’s other 27 updates speaks volumes about how broken many of the Tahoe design decisions were. Apple describes the design as “even more refined,” because in Apple marketing-speak, broken features are never remedied or fixed—past features are just improved. The truth is, Apple has rolled back numerous missteps and made changes to others to mitigate the issues they caused.

Antonio G. Di Benedetto:

The Golden Gate developer beta has proven stable in my everyday use on an M5 MacBook Air and M5 Max MacBook Pro, which is notable since dev betas often have side effects like tanking battery life or causing hardware to run hotter than normal.

[…]

Would I still prefer to go back to the flatter design of macOS Sequoia? Yes, unequivocally. But at least Liquid Glass is more tolerable and less distracting now.

John Voorhees:

Nowhere is the Snow Leopard of it all more apparent than in the hundreds of little changes made to improve the day-to-day use of your Mac. I’m not going to catalog them all here, but I’ve used Golden Gate on two different Macs at this point, and based on my experiences so far, the changes are meaningful.

Jeff Johnson:

This is the crazy Finder column view file selection dragging behavior I’m seeing in the latest Golden Gate developer beta.

Matthias Gansrigler-Hrad:

With the release of the macOS 27 Golden Gate public beta, can we finally submit Mac apps built with Xcode 27?

Previously:

• Golden Gate Spotlight
• Apple Intelligence in appleOS 27
• macOS Touch
• AI-Generated Shortcuts
• Siri AI Announced
• Glow Leopard
• macOS 27 Golden Gate Announced
• Liquid Glass 27 Slider
• Liquid Glass 27 Icons
• Golden Gate Window Corners
• Golden Gate Sidebars and Toolbars
• Golden Gate Menu Icons
• appleOS 26 Public Betas

Apple:

In macOS 28 and later, the Mac OS Extended file system format will be supported only for volumes (disks and other storage devices) that aren’t encrypted. For future macOS compatibility, either decrypt or reformat any encrypted Mac OS Extended volumes.

I think Apple removed the user interface for creating such volumes way back in Big Sur. It’s not really surprising that they’re going away, although only offering a year of warnings seems rather aggressive. Many people delay updating to major OS versions or wait until they get a new Mac. There will be users that switch to a Mac that can only run macOS 28 and get rid of their old one before realizing that some drive they haven’t connected in a while won’t mount.

The other surprising part is that Apple’s options—reformat or decrypt—are not great. During the initial transition to APFS, macOS would transparently convert an encrypted HFS+ boot volume to encrypted APFS without rewriting any data. This functionality is nominally still available via the diskutil apfs convert command, but Apple hasn’t mentioned this or built an automatic upgrader GUI.

[Decrypting] doesn’t apply to encrypted Time Machine backup disks.

It’s obvious why. The old Time Machine format with hard links is totally different from the new one based on APFS snapshots. But this means that you’ll either need to buy a new Time Machine drive for use with macOS 28 or delete your backup history. Even if you keep the old drive, you’ll need an older boot drive or an old Mac in order to be able to access it.

Previously:

• Searching Time Machine Backups and Versions
• macOS 27 Golden Gate Announced
• macOS 27 to Drop Support for AirPort and Time Capsule Backups
• Removing Unwanted APFS Time Machine Backups
• Should You Continue Using HFS+?
• Time Machine Evolution and APFS
• SuperDuper 3.3 for Catalina
• APFS to be Mandatory for SSDs in High Sierra

Update (2026-07-24): Marcus Mendes:

Apple has now revised the page to add a third option, allowing users to convert an encrypted HFS+ volume directly to encrypted APFS without decrypting it first.

[…]

The company has also removed its previous instructions for decrypting the volume first, converting it to APFS without erasing it, and then optionally re-encrypting it.

Hammer:

Ignore Apple’s guidance and do not use Convert to APFS in Disk Utility for disk images.

The first encrypted HFS+ disk image I tried to convert that way failed and left me with an unusable disk image. If I didn’t have backups I’d have lost its contents.

It didn’t corrupt the disk images that I tried, but it didn’t work, either, instead failing with an error about expecting a GPT partitioning scheme.

Update (2026-07-28): Howard Oakley:

As encrypted disk images have never used CoreStorage, withdrawal of support for that has no impact on the continued use of any form of encrypted disk image, including those using HFS+ as their virtual file system.

This is a good point. Apple’s support page refers to “encrypted Mac OS Extended disks,” but the developer release notes refer to CoreStorage specifically. So this shouldn’t affect most encrypted disk images, which show up in Finder as unencrypted after mounting. The encryption is at the disk image level rather than at the file system level. However, I’m not sure that all encrypted disk images are safe. Presumably, a device image, which directly copies the blocks rather than the files, would still use CoreStorage.

Sarah Perez (PDF, Hacker News, MacRumors):

The iPhone maker alleges that this misconduct, which it says reveals a pattern of theft from OpenAI employees who previously worked at Apple, was directed by OpenAI’s senior leadership, including Chief Hardware Officer Tang Tan.

The lawsuit, which was filed in the U.S. District Court for the Northern District of California, accuses Tan of using Apple’s confidential project code names during OpenAI’s recruiting process, asking job candidates to bring in Apple hardware components to their interviews, coaching departing Apple employees on how to evade the company’s security procedures, and asking for details about the company’s unannounced products.

Apple’s allegations are detailed and shocking, and it sounds like they have a lot of evidence.

Chance Miller:

The lawsuit names Chang Liu and Tang Tan as two of the defendants. Tang Tan served as VP of product design at Apple, leading iPhone and Apple Watch product design. He departed the company in February 2024 to work with Jony Ive. Chang Liu, meanwhile, worked at Apple for eight years and was a senior system electrical engineer before departing to join OpenAI in January 2026.

Apple’s lawsuit also names OpenAI and io Products as defendants.

OpenAI’s hardware efforts are being led by Jony Ive, Apple’s former chief design officer.

[…]

Ive, Hankey, and Cannon are not personally mentioned anywhere in Apple’s initial filing today.

Emma Roth:

Here are the most surprising claims in Apple’s 41-page filing.

Marcus Mendes (MacRumors):

OpenAI’s Director of Strategic Communications, Drew Pusateri, took to X to comment on the company’s behalf.

In his post, he claims OpenAI has “no interest in other companies’ trade secrets,” adding that OpenAI remains “focused on building innovative technology that empowers people everywhere.”

This seems like a weak response, given that Apple says it reported its findings to OpenAI in February and never heard back. Presumably, they’ve already investigated but see the situation as serious enough that they need to say as little as possible.

It’s not clear to me the extent to which Apple believes the behavior was limited to the named defendants. It’s hard to believe that the rest of OpenAI’s leadership—including Altman and Ive—were unaware, given the scale of their recruiting from Apple. It’s equally hard to believe that they were aware and thought they could get away with it. I guess little from Altman would surprise me at this point. I’d like to believe that Ive wasn’t part of it, but then are we to believe that his former coworkers all kept him in the dark?

Nick Heer:

What is immediately notable about this whole thing is the myriad conflicts of interest. Apple, of course, has a current partnership with OpenAI to power Apple Intelligence features, something repeatedly mentioned on the previous version of its marketing webpage, and conspicuously absent on the current one.

But the history runs far deeper. Among the defendants in the suit is io Products — do not blame me for that capitalization choice — founded by Jony Ive and acquired by OpenAI last May. Total mentions of “Ive” in the body of this lawsuit? Zero. Also, one of the investors in Ive’s company was Emerson Collective, founded by Laurene Powell Jobs, and which now has equity in OpenAI. Neither Emerson nor Powell Jobs are defendants.

M.G. Siegler:

It all reads a bit as if Apple has been building up evidence of these allegations for some time and recently got their smoking gun. It’s not just nebulous “trade secrets” either, there are specific mentions down to “metal finishing techniques” that Apple apparently invented and protected.

It also comes a little less than a month after OpenAI was rumored to be threatening Apple with a lawsuit over the perceived failure of their deal to bake ChatGPT into the iPhone. As I wrote at the time, even just that threat was clearly not going to go over well in Cupertino.

John Gruber (Mastodon):

Footnote 13 on p. 15 states:

Apple and OpenAI have a commercial relationship involving the integration of OpenAI’s ChatGPT into Apple Intelligence. The companies have entered into a written agreement governing that integration. That agreement is not at issue here. OpenAI’s acts of trade secret misappropriation alleged herein do not arise from and have no connection to that agreement.

Be that as it may legally speaking, in practical terms it seems untenable for that Apple Intelligence partnership to continue after this.

Jason Snell:

All that bubbling-under-the-surface tension between Apple and OpenAI is now out in the open!

M.G. Siegler:

Namely, while Apple frames OpenAI – or at least its fledgling hardware division – as “rotten to its core” (interesting terminology!), they really only have a case against two and maybe three individuals. But they also clearly believe that if this case goes to trial, they will have a case against a lot more.

[…]

The parallels to the Anthony Levandowski situation after he left Google for Uber have been drawn.

[…]

It is interesting that Apple is not suing Yu-Ting “Alyssa” Peng, who is named in the suit as a co-conspirator with Liu while she was still employed at Apple, before she also subsequently went to work at OpenAI. Is it possible she’s cooperating or has cooperated with Apple in this investigation?

[…]

Even if these allegations are found to be untrue or embellished, can he reasonably stay at OpenAI now? And perhaps that’s the real outcome Apple is looking for here, as they clearly frame him as the ringleader of the 400-plus people who have come over to OpenAI from Apple.

Hartley Charlton:

OpenAI’s ambitions to build a hardware rival to the iPhone are already running into trouble because of Apple’s trade secret lawsuit, according to Bloomberg’s Mark Gurman, who argues the damage is showing up well before any court ruling.

[…]

The scale of the talent drain is a major part of why this matters to Apple. More than 400 former Apple employees now work at OpenAI, including former Apple design chief Jony Ive, and Gurman says the company poached so heavily from Apple’s iPhone product design group specifically that Apple had to rebuild parts of the team. Apple has responded with bigger retention bonuses and executives personally working to keep engineers from leaving.

Jeff Johnson:

OpenAI stole stuff? I can’t believe it! I thought they were done with stealing after they stole literally everything on the internet.

Colin Cornaby:

I’m sure there’s no problem with sending this company all your source code they pinky swear not to train on.

Steve Troughton-Smith:

I can’t believe this awful company solicited confidential information and stolen trade secrets, hiring from this other company while pretending to partner with them. ‘Rotten to the core’ indeed

😛

He’s referencing Apple doing this to Masimo. And, of course, Steve Jobs himself directed Apple to engage in illegal hiring practices.

Previously:

• OpenAI Acquires Jony Ive’s io
• Apple v. Optis Cellular Technology
• OpenAI to Become For-Profit Company
• OpenAI and Ive
• Masimo v. Apple
• OpenAI Is Today Unrecognizable
• Inside Apple’s Design Team
• BlueMail Antitrust Case Against Apple Dismissed
• Apple Suing Former A-series Chip Lead
• Apple/Google Hiring Lawsuit, Settled

Update (2026-07-17): See also: Dithering.

Tim Hardwick (FT, Hacker News):

Apple has reportedly sent legal letters to dozens of former Apple employees now working at OpenAI, telling them to preserve potentially relevant documents and communications as it continues to pursue its trade secret lawsuit against the AI company.

Update (2026-08-06): Hartley Charlton (PDF):

OpenAI has asked a federal judge to dismiss Apple’s lawsuit accusing the AI company of stealing trade secrets, calling the allegations “meritless.”

Previously:

• OpenAI Open Letter Responds to Apple Lawsuit

John Gruber, earlier this week:

When ChatGPT is attached to an open document in another app, it’s not a snapshot at the moment of attachment, like what you’d get by copying and pasting the whole thing into the chat, or by dragging the current version of the file into the chat. It’s a live ongoing attachment, so as the attached document/note changes, ChatGPT sees the changes. It’s such a great feature, and I don’t think it exists on any platform but the Mac. And it couldn’t exist on iOS, by design, doesn’t allow for inter-application communication.

I worry for ChatGPT’s future, though.

Juli Clover:

OpenAI today announced ChatGPT Work, a ChatGPT agent with built-in Codex that can complete tasks across web, mobile, and desktop using information from your apps. ChatGPT Work can execute multi-step tasks, using scheduling to work independently. Like Claude Cowork, ChatGPT can use your computer to do tasks in the background across apps.

[…]

With OpenAI merging Codex and ChatGPT, there is a new ChatGPT desktop app that’s available across Mac and Windows. Users who have the Codex app installed can update it to turn it into the new ChatGPT desktop app. The existing ChatGPT desktop app is being renamed ChatGPT Classic.

Zac Hall:

You can watch today’s livestream announcement video below[…]

[…]

It’s possible to have ChatGPT Classic, ChatGPT, and Codex installed, but the way forward seems to be just running the new ChatGPT desktop app. Codex users can still use the Codex app icon, but the app will be called ChatGPT.

The ChatGPT Classic app looks more native Mac-like, so that might be an issue for users.

Steve Troughton-Smith:

LOL @ OpenAI replacing the native AppKit ChatGPT app with the Electron Codex app after @gruber’s recent posts on the topic 😂

(It’s almost like Apple doesn’t have clear messaging on the right way to build native desktop apps anymore, and, if Apple doesn’t know, why on earth would third-party developers make that investment)

Federico Viticci:

The rollout of the unified ChatGPT for Mac app really isn’t going well on X/Reddit 🥶

They kinda fumbled it and I think Anthropic did a slightly better job on first try. Even OpenAI’s existing iOS app makes more sense than their new Mac layout right now.

The difference between “normal” chatbot chats, Work/Cowork harnesses with connectors, and Code/Codex local threads and filesystem access is the new UX hell for these companies.

Steve Troughton-Smith:

The chat experience is ChatGPT. Now it’s squirreled away in a sub section of a sub pane inside a vastly more-complex app. It’s hard to imagine anybody who actually wants to use ChatGPT wants to use it this way, Electron or not. And as a Codex user, I resent having my Codex deleted and renamed ‘ChatGPT’ instead. I don’t want my ‘chats’ anywhere near my ‘work’. This feels like a stupid move that will decimate casual ChatGPT desktop usage

John Gruber (Mastodon):

Looks like I picked the wrong week to quit sniffing glue.

See also: Dithering.

Previously:

• Sunsetting ChatGPT Atlas
• Claude Desktop App
• Gemini App for Mac
• Codex App

Update (2026-07-13): Tony Arnold:

Oh yeah, the new ChatGPT app is as bad as first impressions made it out to be. It’s not just a slow, RAM hungry shell of a thing, but the design and UX are a poorly thought out kitchen sink approach.

Codex has never been great, but this is a confusing mess.

Benedict Evans:

Wow, what a total mess. What is the difference between a project, a task and a chat? Why did chats get a crappy floating window but tasks and projects don’t? Why does choosing ‘plugins’ get me ‘templates’? Am I not allowed to finish ‘setup’ if I don’t use Slack or Google Drive? Why…

Via John Gruber (Mastodon):

OpenAI’s internal org chart is a complete disorganized mess. This new app perfectly reflects that.

The old ChatGPT app was focused. That’s the app that still ships for mobile (which includes iPad, which tells you whether OpenAI thinks iPad is a real computer or a big iPhone), and is, for some Mac users, left installed on their systems as “ChatGPT Classic”. The new app is an incredibly confusing sloppy mess. At a glance it looks like a polished app. But the UI is just slop. It has the veneer of a polished app without actually being organized or structured or labeled in ways that add clarity and coherence.

John Gruber:

So I don’t see “the prompt in the app to download the new ChatGPT desktop app”. If I download the new app manually, I get a disk image. After mounting the disk image, the instructions say to double-click the “ChatGPT” app on the disk image — not to drag it to the Applications folder. If I do that while the old ChatGPT app is still running, it bounces back and forth a few times but nothing new gets installed and nothing old gets removed or renamed. I’m just left with the classic ChatGPT app, still named “ChatGPT”.

If I run the installer on the disk image when the old ChatGPT app is not running, the old app gets replaced by the new one in my Applications folder, and the old app is moved to the Trash. There is no app named “ChatGPT Classic”.

I mean, their Help document does say “the new app may install alongside your current app”, and “if both remained installed”, so they seem just as confused as I am.

Update (2026-07-14): Adam Engst:

And as much as I’ve been focusing more of my attention on Anthropic’s Claude because of concerns I have about OpenAI and its management, ChatGPT has more active users (~1.1 billion) than Google’s Gemini (~900 million), and many more than Claude (~245 million, in part because it’s more focused on enterprise uses).

As such, it’s worth noting three recent changes with ChatGPT: a massively confusing app replacement, the end of the ChatGPT Atlas Web browser, and improvements to ChatGPT Voice.

Update (2026-07-17): M.G. Siegler:

Let’s give OpenAI some credit, once they realize they made a mistake, they act quickly to correct it. Today’s case in point: with an update, ChatGPT now features ChatGPT once again. No, that’s not a joke, and yes, it does speak to a very obvious self-own.

John Gruber:

How in the world did they ship this without sync?

[…]

Bringing back “chat” to ChatGPT is literally the least they needed to do. Hiding chat in an obscure corner of the interface from an app named “ChatGPT” would be like removing text editing from TextEdit.

James Sun (via Tim Hardwick):

Lastly, with all these updates, we are going to be sunsetting Atlas.

All these capabilities were built on what we learned from Atlas users who took a leap of faith on a new browser.

You taught us how agents can help make browsing and doing work on the open web better, and we are applying these learnings to these new products.

Zac Hall:

With the new ChatGPT desktop app, OpenAI now has a desktop app with robust browser capabilities. ChatGPT (and Codex before it) also supports a Chrome desktop browser plugin. This lets Chrome users benefit from ChatGPT integration without completely switching browsers.

Kyle Hughes:

Anthropic and OpenAI have legacy software media in the blender because they are playing a new game. They are legitimately racing to build God. The products they release are one-off fundraising vehicles to buoy the next training run. They are not trying to build long-term consumer goodwill.

Previously:

• ChatGPT Work and ChatGPT Classic
• Codex for Almost Everything
• Discontinuing Sora
• Codex App
• ChatGPT Atlas
• AI in Chrome, Neon, and Dia

Howard Oakley:

Spotlight doesn’t currently appear able to search Time Machine backups reliably, at least not in Sequoia or Tahoe, although this may not be universal.

[…]

If I now step back through my backups to reach one that I know contains that file, I can restore it. But if I type anything into the search field, nothing is found. If I change the scope of the search to that backup, the window title changes but its contents remain blank, and there isn’t even a busy spinner to indicate a search is in progress.

[…]

As I can’t disable Spotlight indexing on that volume without macOS telling me that it’s required to be indexed by Spotlight, neither can I force that volume to be reindexed.

[…]

My conclusion is that using Spotlight to search Time Machine backups no longer works, and the instructions given by Apple are also broken.

That has been my experience, too. As I see it, there are four separate problems:

1. I want to be able to search all my backup snapshots, because I don’t know which one might contain the file I want to restore. Time Machine only lets you search one at a time.
2. Searching an individual snapshot doesn’t actually work.
3. Spotlight indexing is invasive, using lots of CPU time, and with spinning hard drives causes wear and tear and creates lots of noise. If search doesn’t work anyway, I’d like to turn it off, but macOS won’t let me.
4. If the problem is with the index, there’s no way to reset it without deleting your backup.

Howard Oakley:

Unfortunately, all those saved versions in the version database fall outside the scope of Spotlight indexing, and Spotlight search can’t look inside any of the old versions saved in a volume’s version database. Surprisingly, the version browser doesn’t offer any search facilities either, as that’s presumably another feature intended for a future that never came.

[…]

One way around this is to save each document version as a separate file, allow Spotlight to extract their contents and add those to its indexes for that volume, then to search those files. This is quick and simple using my free utility Versatility.

Previously:

• Golden Gate Spotlight
• Time Machine in Tahoe
• Runaway Spotlight With Pages Document on iCloud Drive
• Spotlight Indexing Running Wild
• Invasive Spotlight Indexing
• You Can’t Turn Off Spotlight on Your Time Machine Backup

Mike Bombich:

The USB device drivers report that they are destroying the “Rocket XTRM Q” device due to a “link change interrupt”

APFS filesystem drivers report a “dangling mount”, failures to finish transactions before unmount, and dozens of “media is not present” errors.[…]

storagekit collects a report of the “disappeared” devices and notices that one of them was mounted. This is ultimately what leads to the “Disk Not Ejected Properly” notification.

Unfortunately, nothing in here explains what caused the “link change interrupt”; all we know is that the USB device drivers detected an interruption.

Not discussed here, perhaps because there’s little we can do about it, is the role of changes to macOS. I’ve documented problems in the past of hard drives, which used to work perfectly, suddenly start spontaneously unmounting with every backup after updating to a new OS version. The Sierra to Big Sur period was particularly bad, as I recall. (There are also some hard drive enclosures, and cheap SSDs, that seem to be problematic to matter the OS version, but I don’t continue to use those.) Sometime around Monterey or Ventura, the spontaneous unmounts almost completely disappeared for me, though Ventura introduced other mounting/unmounting problems. Last week, I finally updated to Tahoe, and I’m sad to say that spontaneous unmounts are back. Almost every night, one of my Samsung SSDs—connected to a Thunderbolt dock—gets reported as improperly ejected. Sometimes it remounts by itself; other times I have to unplug and replug it.

Previously:

• Upgrading My Mac’s External SSD
• Remaining Issues in Big Sur
• OWC Dual Drive Dock USB 3.1
• Some Known Bugs in macOS 10.12.6
• RocketStor Drive Dock: More Expensive But Reliable
• Highpoint RocketStor 5212 Thunderbolt Dual Drive Dock
• Ejecting External Disks With macOS 13
• Ventura Issues

Update (2026-07-09): Rosyna Keller:

I keep getting these errors too. It only started when I connected the external SSD to a OWC Thunderbolt dock. It never happened with direct connect.

My Thunderbolt dock is from Anker.

Update (2026-07-10): Matt:

I also just stared getting these a bunch. Mine is connected to a CalDigit Thunderbolt dock.

I have to wonder if something changed in a recent update (15.7/26.4?)