EagleFiler 1.9.18 is a maintenance release of my digital filing cabinet and e-mail archiving app. This version adds support for macOS Tahoe 26, amongst other enhancements and fixes.
Some interesting issues were:
A new Liquid Glass icon is in the works, but for now it uses -[NSApplication setApplicationIconImage:] and -[NSImage setName:] to break the icon out of squircle jail in the Dock and in windows throughout the app.
Tahoe has a new font panel, and accessory views for it would cause crashes for most of the beta cycle. This seems to have been fixed in developer beta 6.
Each major macOS update seems to add a few symbols that cause crashes when imported by the old, customized version of PyObjC that I’m using. This time, it was BSXPCServiceConnectionProxy<BKSHIDEventDeliveryManagerServerInterface> in AVPlayer.
The main EagleFiler executable is not compiled with Xcode 26 because doing so breaks one of the app’s key split views. I’m not exactly sure what’s going on, as the app only uses split views in the most basic way. I’m in the process of rewriting it to use NSSplitViewController, which seems to avoid the problem. But, for now, since it’s linking against an older SDK for compatibility, this means it won’t get the new Tahoe window toolbar style yet.
Tahoe has some regressions that affect conversion of HTML to RTF and plain text. Some lists lose their numbering, and there are also spacing changes (FB18655613).
Previously:
Cocoa EagleFiler HTML Icons Mac Mac App macOS Tahoe 26 Programming PyObjC
Apple (downloads, releases):
Xcode 26 beta 6 includes SDKs for iOS 26, iPadOS 26, tvOS 26, watchOS 26, macOS Tahoe 26, and visionOS 26.
[…]
Fixed: The coding assistant can be disabled via device management in Xcode 26 Beta 6 by setting CodingAssistantAllowExternalIntegrations to false in a configuration profile with a com.apple.dt.XcodePayloadType.
This is the only beta 6 change in the release notes, however Apple has now added documentation for lots of changes in beta 5.
Previously:
Mac macOS Tahoe 26 Programming Xcode
Victor Wynne (via Hacker News):
Apple’s latest addition to Xcode, the Processor Trace instrument, is one of those features that sounds pretty mundane until you actually try it. Then you realize it’s exactly what you’ve been needing for the performance mysteries that eat up hours upon hours of your development time.
If you’ve been developing apps for a while, this story will sound very familiar. Your app runs fine in testing, but then users complain about performance issues or excessive battery drain. You fire up Instruments, poke around with Time Profiler, and maybe get some clues about which functions are eating CPU cycles. But often you’re left guessing about what’s really happening at the processor level. The true black hole of development work.
That’s where Processor Trace comes in. This tool captures every single branching decision your code makes at the CPU level, then presents it in a way that actually makes sense. Instead of statistical sampling like most profilers, you get a complete picture of your app’s execution flow. It’s the difference between taking random snapshots of a busy intersection versus having a complete video recording of all the traffic passing through.
See also: WWDC 2025.
Miguel de Icaza:
God I love Instruments.
And to think that Microsoft killed our awesome Instruments-inspired profiler for C# and people have to use that tasteless and useless profiler on windows.
Previously:
Apple M4 Debugging Developer Tool Instruments iOS iOS 18 iPhone 16 Mac macOS Tahoe 26 Optimization Processors
James Cridland:
Running the Mac OS 26 beta (I know, I know), but running out of hard drive space. Turns out the reason is that half of my drive is full of “System Data”.
Internet searches are not very helpful in terms of how to reclaim this space. I’ve tried booting into safe mode and back, but wherever these files are isn’t visible to anything like DaisyDisk to check further and/or persuade them to go away.
Kornel:
I had a similar issue on my beta 5, updating to beta 6 didn’t fix anything. Additionally, there seemed to be a memory leak within the mds_stores process, which was using a lot of my memory and it was increasing every second up until it started using my swap.
I couldn’t find a solution, so I backed up my Mac (created a clone using SuperDuper!), clean installed beta 6 again and restored my backup. Issue is gone, reclaimed over 100 GB of free space and System Data now shows around 26 GB.
Sarah Reichelt:
I had this with beta 5. It was crazy watching the disk space tick away for no reason. Beta 6 fixed it, at least so far it has.
I’ve had lots of problems with Tahoe operations (primarily xcodebuild) failing because it reported no free space, and this continued with beta 6. Whenever this happened, Finder and Disk Utility would both show about 40 GB of free space. There did not seem to be any hidden usage due to snapshots, which makes sense since I’m not backing up that Mac installation. I have no idea what else would be using the space, why it doesn’t see to show up as used anywhere, nor why it eventually seems to clear up on its own, but only for a time.
Previously:
Mac macOS Beta macOS Tahoe 26 Spotlight Storage Xcode
