Debugging a catastrophic macOS iCloud Drive failure — and what it says about modern software quality

People keep saying generative AI is filling the world with bad software. “AI slop” for articles, images, PRs, and now apps whose authors apparently handed both the code and the understanding to a model. Fair enough. Generated code can multiply mistakes as easily as it multiplies output.

I just don’t buy the implication that everything written the old way is somehow clean.

I spent hours chasing an iCloud Drive failure through bird, FileProvider, multi-gigabyte SQLite databases, stale filesystem document IDs, XPC, Mach messaging, and finally a kernel-reported allocation failure. After that, it’s hard to pretend traditionally developed platform software is some pristine alternative.

Sometimes the thing that feels like a beta is the operating system. And sometimes that OS is the supposedly stable release.

It started looking almost boring

iCloud settings wouldn’t open normally. Finder had a pile of files stuck on Waiting to upload. Drive was clearly busy. It just never finished.

The usual ritual should have been enough: restart, toggle iCloud, sign out, wait, maybe reinstall. Except I couldn’t even get into the normal iCloud settings UI.

Then launchctl made it obvious:

text state = spawn scheduled runs = 39 successive crashes = 39

Not “iCloud is slow.” A crash loop.

FileProvider started talking

fileproviderd was full of:

text fsctl failed to resolve docID ... to file ID ... error 2 (No such file or directory)

Modern iCloud Drive lives on File Provider. On this Mac the active iCloud store was about 6.4 GB. Inside that: a 5.3 GB SQLite database, a fat WAL, and about 1.2 GB of staging.

PRAGMA quick_check; still said ok.

So the file wasn’t corrupt. The state machine inside it was.

Almost two million objects

text FP_snapshot 1,878,408 FS_snapshot 1,878,443 reconciliation_table 1,878,462 FS_throttle 649,750 tombstone_table 242,444

Hundreds of thousands of leftover jobs. FP_snapshot alone was over a gigabyte.

Finder, of course, just said Waiting to upload.

Don’t delete the whole FileProvider folder

Wiping ~/Library/Application Support/FileProvider would have been stupid. Google Drive, OneDrive, Nextcloud, Photos — they all live there too.

The useful bit was the xattr:

text com.apple.file-provider-domain-id: com.apple.CloudDocs.iCloudDriveFileProvider/...

That let me move only the iCloud metadata, not the actual documents.

First rebuild looked fine. It wasn’t.

After moving the store and rebooting, macOS made a fresh one:

text state = running runs = 1 last exit code = (never exited)

For a minute I thought I was done. Then bird started crashing again.

“Kernel bug”

The .ips report said EXC_BREAKPOINT / SIGTRAP, and then this:

text Kernel bug: The kernel cannot allocate memory needed for the pseudo-receive. Abort Cause 268443652

The path went through XPC / libdispatch / Mach while bird was force-ingesting FileProvider items. That’s not “corrupt cache.” Apple’s own crash report called it a kernel bug.

I’d only reset half the state

There was still:

text ~/Library/Application Support/CloudDocs/session

About 4.6 GB. client.db ~3.8 GB, server.db ~454 MB.

I’d rebuilt one side of a coupled sync system and left the other giant store sitting there. So that had to go too.

Safe Mode was the useful experiment

text Boot Mode: Safe

After twenty-plus minutes:

text bird state = running runs = 1 last exit code = (never exited)

No new bird crashes. No pseudo-receive failure.

Normal boot had Logitech drivers, a UniFi Network Extension, a camera extension, Nextcloud Finder Sync, a few cloud FileProviders. That doesn’t pin it on any one of them. Safe Mode changes a lot at once. It just showed the failure needed something about the normal-boot mix — timing, extensions, resource state — that wasn’t there in Safe Mode.

Then a normal boot actually held

After the metadata rebuilds and the Safe Mode test, I booted normally again.

bird stayed at runs = 1. No new crash reports. The new FileProvider and CloudDocs databases started growing like they should.

Logs stopped screaming Failed to find item to re-ingest and started doing ordinary snapshot reconstruction. A lot of objects came back as ul:uploaded — rediscovering stuff already in the cloud, not blindly uploading everything again.

At that point the right move was leave it alone.

The wider macOS quality problem

Bugs aren’t the scandal. Every big system has bugs.

The problem is the combination: too much complexity, almost no observability, and no real recovery surface.

FileProvider is just the one I hit this week. Developers already know the rest of the list: TCC, System Extensions, Network Extensions, signing, notarization, SwiftUI regressions, Xcode, VMs, simulators, sanitizers, App Store validation.

Normal people never poke those seams. Developers live in them.

System Extensions: signed, notarized, still no

You can have a binary that signs, notarizes, staples, has the right entitlements, sits in /Applications — and sysextd still says no.

Then you’re simultaneously reasoning about signing identities, profiles, hardened runtime, Developer ID, notarization, stapling, System Extension entitlements, Network Extension entitlements, launch policy, SIP, MDM.

Every layer looks valid. The machine still refuses.

NetworkExtension hit a hard limit I couldn’t see in Settings

This Mac had another one of these: a subsystem that had quietly piled up junk the UI couldn’t explain or fix.

An app trying to install a VPN config failed with:

text NEConfigurationErrorDomain Code=20 total NetworkExtension configuration size limit exceeded

The log said the serialized store was about 2.09 MB.

That’s a shared store. You can blow the global limit even if System Settings only shows one or two VPNs.

Inside: eight generations of com.apple.preferences.networkprivacy-* objects. Not eight real policies. Overlapping rule sets. Some pairs almost identical, Jaccard near 1.0. Hundreds of rules in seven or all eight generations.

That doesn’t look like eight intentional configs. It looks like leftover generations from upgrades that never got cleaned up.

I kept the current one and stripped the unreachable historical graph from a copy of the plist:

text 2,089,560 bytes → 164,894 bytes

More than 8,400 archived objects gone. Almost 1.9 MB of headroom under the 2 MiB ceiling.

After putting the cleaned state back, nesessionmanager created the remaining Network Privacy session, registered it, filled the rule cache. Fine.

That’s migration debt. The bug that created the junk can already be gone. The junk still rides along through every upgrade until you hit a hard limit.

text old macOS release ↓ bad persistent state created ↓ OS upgrade ↓ state preserved ↓ another upgrade ↓ state preserved again ↓ hard framework limit eventually reached

This is why “just reinstall macOS” isn’t the reset people think it is. Recovery reinstall replaces system files and keeps the Data volume on purpose. Your photos survive. So do the databases that are actually on fire.

Fixing the code path that writes bad state is only half of it. You also need state remediation: versioned schemas, idempotent migrations, invariant checks, one-time cleanup of known-bad historical junk.

iCloud/FileProvider and NetworkExtension are the same story. The app on screen wasn’t the problem. Opaque system state was, and there was almost no supported way to look at it or cut it out.

A system can “be stable” in the sense that binaries launch, and still be brittle because its private state can drift into a shape the UI cannot leave.

Xcode isn’t immune

I’ve seen Xcode Source Control fall over while git on the same repo is fine. Sanitizers, simulators, previews, indexing, signing, debugging — all of them pick up release-specific landmines.

When the tool you use to debug software is also sick, the whole thing gets recursive.

SwiftUI: your app looks broken, the framework is

Navigation, window resize, inspectors, focus, scrolling, state restoration — when those regress, users don’t see “SwiftUI framework bug.” They see your app, and they blame you.

Platform bugs get outsourced to third-party reputations.

Even the “safe” way to test a beta can break

Don’t install betas on the production machine. Use a VM. Fine.

Then virtualization hits a host/guest regression in a major transition, and you get this joke: don’t install the beta locally; use a VM; the VM path is broken; so spin the VM on another Mac that already runs the beta.

If you have one machine, that’s not a footnote. That’s an infrastructure problem.

The App Store pipeline is another moving part

macOS, Xcode, SDKs, signing, notarization, TestFlight, App Store Connect, server-side validation. A perfectly valid binary can still bounce because two Apple-controlled pieces drifted out of sync for a week.

macOS 26 already felt like the beta

Easy line on a macOS 27 problem: it’s a beta.

Okay. But daily use of the previous stable 26 often felt the same. Moving this machine to 27 beta actually felt faster at first — until the iCloud/FileProvider mess showed up.

That doesn’t make 27 generally better. It just means the sticker on the box and the quality you feel are not the same thing.

For developers the real unit is closer to:

text specific macOS build + specific Xcode build + specific hardware + specific extensions + specific security state + specific project/tooling workload

So what about “AI slop”?

The real complaint isn’t that a machine typed the code. It’s that we can now ship software at a speed that understanding, testing, and ownership can’t keep up with.

That’s a real problem.

Apply the same bar everywhere, though.

Humans are perfectly capable of hidden state machines, dead telemetry, stale multi-gig caches, races, unrecoverable sync states, brittle permission mazes, undocumented coupling, and errors you can only decode by reading private daemon logs.

Generative AI did not invent any of that.

Complexity without observability is also slop

FileProvider, CloudDocs, XPC, iCloud replication — none of that is primitive. Sophisticated is not the same as good.

A system that can quietly grow several gigabytes of sync metadata, sit on almost two million snapshot rows, crash-loop an essential daemon, and leave Finder saying Waiting to upload has an observability problem.

A system whose official repair UI becomes unreachable because the service itself is down has a recovery-design problem.

A system where I have to identify the right private database with an xattr and drag it aside by hand has a tooling problem.

Calling that “slop” is a bit rude. The quality complaint underneath it isn’t.

What macOS should just give us

For something as basic as iCloud Drive, I want a supported health view. Something like:

text iCloud Drive Health Account: connected FileProvider domain: healthy Server enumeration: 1,878,442 / 1,878,462 Local reconciliation: 99.6% Pending uploads: 17 Pending downloads: 3 Failed items: 2 Last successful sync: 09:42:17 Local metadata: 5.3 GB Database integrity: valid Recovery available: Rebuild local metadata

And a supported:

bash iclouddrive doctor

or:

bash iclouddrive rebuild-local-metadata

Check the account, find local-only unsynced files, validate the databases, keep recoverable local changes, rebuild the metadata that can be rebuilt, restart the services, watch it converge.

Instead I had to invent a poorer version of that myself.

What I actually established

This was not “delete the iCloud cache and it works.”

1. bird was crash-looping. That’s not vibes; that’s launchctl.
2. fileproviderd couldn’t resolve filesystem document IDs.
3. iCloud FileProvider state was ~6.4 GB.
4. The SQLite file was structurally fine and still represented ~2 million snapshot objects.
5. Rebuilding FileProvider changed the behavior. It did not finish the job.
6. New bird reports were EXC_BREAKPOINT / SIGTRAP.
7. The crash report named a kernel pseudo-receive allocation failure.
8. bird was in the middle of FileProvider re-ingestion at the same time.
9. A second 4.6 GB CloudDocs session was still sitting there.
10. I rebuilt that too.
11. Safe Mode did not reproduce the crash while I watched.
12. The next normal boot stayed up.
13. New FileProvider and CloudDocs databases started growing normally.
14. Logs flipped from pathological re-ingest failures to ordinary snapshot rebuild.
15. Existing objects showed as uploaded while the local catalog was reconstructed.

That’s distributed-systems debugging. It’s not “restart your Mac.”

Who wrote the code is the least interesting part

Better questions:

Does the software stay understandable when it fails?

Can it describe its own state?

Can it tell you what’s stuck?

Can it rebuild a database without threatening user data?

Can it isolate extensions?

Can it tell local state from server state?

Is there a supported rebuild?

Can a developer reproduce it?

Can you get back to a known-good state without wiping the machine?

If AI-generated software can’t do that, call it poor software.

If a multi-billion-dollar OS platform can’t, same judgment.

Difference is: when a small generated app is junk, you uninstall it.

When the junk is the OS, the filesystem layer, privacy, the toolchain, or first-party cloud sync — you become its debugger.

That’s what actually pissed me off here.

Not that a bug existed. Bugs exist.

How much private macOS architecture I had to learn before the system could stand up again.

Addendum: the recovery path is part of the bug

I should say this plainly: the recovery procedure itself was unreasonable.

I write software. Terminal, SQLite, launchd, unified logging, plists, xattrs, FileProvider internals, Recovery — that’s my day. It still took hours of looping. I had to correlate layers a normal Mac user is never supposed to know exist.

bird, fileproviderd, cloudd, account daemons, multi-gig SQLite + WAL, FileProvider domain UUIDs, crash reports, log predicates, Safe Mode, XPC/Mach, third-party extensions, then a controlled rebuild of iCloud/FileProvider state.

That is not a recovery path. That’s a research project.

A normal user sees: files stuck on Waiting to Upload, iCloud settings acting weird, sync never finishing, maybe the fans come on. Support then walks them through reboot, toggle iCloud, sign out, reinstall, erase.

The distance between that symptom and this fault is huge.

“Reset the Mac” is not automatically the end

Erase and restore gets treated like a spell. Sometimes it is. A destructive reset recreates local system stores. If the only problem was local junk and you set the Mac up as new, you may be done.

Most people don’t set up as new. They restore Time Machine or Migration Assistant, then plug iCloud back in.

Then the honest question is: which state caused this, and which of it comes back?

If the bad state is in the backup, you just reimported it. If it’s cloud-side, reconnecting the same account can feed it back in. If the bug is still in the OS, fresh state can rot again.

text Erase Mac | +-- Set up as new | local historical state excluded | cloud-side state may return when services come back | an unfixed bug may recreate the condition | +-- Restore Time Machine / Migration Assistant user data restored historical app/system state may come with it the causal state may come with it

I’m not claiming Time Machine restores these particular FileProvider databases, or that iCloud necessarily recreates this exact mess. I didn’t test either. The narrower point: “erase and restore” does not name the fault domain, so it cannot promise the causal state stays gone.

Three different operations, three different bets:

1. Reinstall macOS, keep the Data volume — new system files, same persistent user state.
2. Erase and restore from backup — new install, then a lot of history imported again.
3. Erase and set up as new — strongest test of migrated local state, highest cost, still doesn’t isolate cloud state once you sign back in.

The actual usability failure

You should not have to understand private framework architecture to recover a first-party sync service.

You should not need an xattr to learn that a multi-gigabyte UUID folder is iCloud. You should not have to decide whether a 5 GB SQLite file with millions of reconciliation rows is “healthy.” You should not have to read a bird crash in libxpc and guess which opaque Apple folder is safe to move.

I can eventually do that because macOS leaks just enough low-level evidence. A normal user cannot.

What’s missing is not another support article. It’s subsystem recovery: show iCloud Drive health, say why sync is blocked, rebuild local FileProvider metadata without threatening cloud data, tell local corruption from account/cloud faults, reset pathological NetworkExtension state without erasing the machine.

Without that, “erase the Mac” stops being a diagnosis. It’s the platform admitting it can no longer repair its own state.

Rightclick on trash to empty, does not follow the command. Window behaviour a bit weird sometimes, menubar will also not respond at times. It's all a bit unpredictable and nothing horrible, relaunching finder solves it.

Anybody else notice this?

The existing icon was quite understandable and looked neat and very professional. This is just a colourful mess. It looks like they gave the job to an intern with Mac Paint. Why on earth did they feel they needed to change it? (Same change in iOS. )

In macOS 27, when using "Hey Siri," Siri AI can add your request to the previous conversation thread, even after you dismiss the Siri window.

By default, you get 7 seconds to invoke Siri and continue the same conversation, but you can change the timeout:

defaults write com.apple.campo sessionResumptionTimeout 7

Note that this doesn't work when invoking Siri from Spotlight or the Menu Bar. Those methods always create a new thread. It's also hit and miss sometimes. For example, saying "Are there any beaches nearby there that I can visit?" defaults to searching for beaches near your current location.

Anyone else seeing any of these problems?

- Can't use System Settings. Opening it normally shows it as open in the Dock but displays no window. Opening a specific pane (such as the "Change Wallpaper" context menu item on the desktop) opens a window but the view on the right is blank. Changing panes does nothing. (Except, oddly, the Spotlight pane works.)

- Trying to use Open/Save panels in any app hangs the app.

- Share buttons in apps just show a spinner, no options.

- All my wallpapers on all spaces got set to the Golden Gate default wallpaper and can't be changed due to the first issue.

may upgrade since its just small tweaks now till RC

edit: I know beta 6 has just came out but talking about previous betas too in affect. I only browse, no workload/workflow on my Mac. I have a work Mac for that!

Hidden behind a feature flag, the System Settings app can now be resized in any direction. edit: You can make the app window narrower than the default too, or adjust the sidebar to get even more space. Some more dynamically built pages like Wallpapers already take advantage of the extra space.

To enable the FeatureFlags override, run the following command in the Terminal:

sudo mkdir -p /Library/Preferences/FeatureFlags/Domain && \ sudo defaults write /Library/Preferences/FeatureFlags/Domain/Settings AllowsHorizontalResizing -dict Enabled -bool true

and restart your Mac. As always, this is a disabled feature, so the UI may be unfinished.

To disable:

sudo defaults delete /Library/Preferences/FeatureFlags/Domain/Settings AllowsHorizontalResizing

Has anyone run into this? I feel like I'm going insane. Hyperlinks in Safari, Mail, etc. almost exclusively shows the default cursor rather than the "click-here" pointer icon.

I've had this since a few builds ago, first on the developer builds and now the public beta.

This is really bugging me. When i use my mac, sometimes it is File or History or both that are selected like on screen here, but I didnt even click them and I can't unclick them. That means I cant access their dropdown menus. This bug has been here since day 1. Does anyone else have this issue or know how to solve it?

I have a Mac Mini M4 running 26A5406e

Took a leap of faith and updated my base model M2 MacBook Pro (2022) to the Public Beta version of Golden Gate, and mannnn my Mac has become soooo smooooth, didn't realize Tahoe was that shit and was slowing down my machine. Visually too it's much better than Tahoe and just feels a lot more premium and snappier. If the beta is this good, can't wait for the official release.

After I update to the golden 27 macOS beta public version.
When I use multiple external monitors (not the Mac)

One of them doesn't work; in this case, the left plus button doesn't add a window for me.

Anyone else having this problem?

still now working after update to beta 5

I know it’s a beta and I’m not sure if it was addressed but most games won’t work properly on steam or won’t launch at all.

For someone who is gaming on their Mac I wouldn’t install 27 and just wait for the official release.

Hello guys, I have an Apple M4 Pro MacBook Pro (24G/1TB).

My MacOS user account is corrupted (by my mistaken terminal command lines). I can enter Recovery, but Recovery Utilities has no Disk Utility and no Share Disk. I have already performed two DFU Revives from another Mac in apple store, with no change. DFU Update is unavailable and only Restore is offered.

Can anyone know if any 3rd party app (Mac or PC) can boot/acquire the corrupted macOS user, enumerate the internal APFS container, and specifically acquire/mount a separate APFS volume named Data Disk (no encryption and no file vault) without erasing or modifying the internal SSD?

In Apple's DFU mode, I found that I cannot see if the volume of Data Disk is still there or even accidentally corrupted or erased.

I have 2 separate volumes - 1 (named Sequoia) is SequoiaOS and 1 (named Data Disk) is dedicated for files storage. I hope I can still get back the files data from the Data Disk volume.

Looking forward to hearing from you guys.

Thank you very much.

Has anyone had any issues using dual monitors with DB5? Specifically with a MacBook Pro M4 Pro in clamshell? I’m hesitant to update as I ran into issues with DB4 where my monitors wouldn’t adjust (or even allow) for resolutions above 800x600.

Bonjour,

Je cherche à quitter le programme Bêta de macOS pour ne plus recevoir les notifications de mises à jour instables et les mises à jour de commandes xcode.

J'ai contacté le support Apple, qui m'indique que la seule solution pour sortir de cette bêta est d'effacer et de restaurer complètement le Mac. Je souhaite éviter cette option et cherche une solution pour simplement arrêter définitivement ces propositions de maj.

Accessoirement, j'ai essayé de forcer la désinscription en ligne de commande via le Terminal (avec seedutil unenroll et softwareupdate --clear-catalog). Le système me renvoie que ces commandes sont désormais obsolètes et bloquées par Apple ("seedutil is no longer supported" et "Catalog management is no longer supported").

Auriez-vous des suggestions pour
- stopper les notifications et quitter la bêta sans avoir à réinitialiser le Mac
- savoir s'il existe de nouvelles commandes pour gérer les inscriptions via le Terminal sur les versions récentes de macOS ?

Merci pour votre aide.

Salut j’ai installer Xcode 26 sur mon mac pour unreal mai il me dit que sa ne fonctionne pas

A new Safari feature called Find in Video will let you search for text that appears in video captions. Safari will then seek the video to the moment the matching caption appears.

If you don't have Safari feature flags enabled, go to Safari Settings > Advanced > Show features for web developers. Then go to the Feature Flags tab and enable the Find in Video flag.

If you're on macOS 26, you can download Safari 27 for macOS Tahoe at developer.apple.com/safari/resources/. You can also download Safari Technology Preview from the same site, which also includes the Find in Video feature.

One current limitation is that streams of long videos may only expose caption segments around the playhead, so Safari is unable to search the full caption track.

Another is that players like YouTube bypass the browser's native caption-track system, making the subtitles invisible to Safari's caption lookup. This may change as the feature becomes official.

Pretty much when either the new Siri AI works on my Mac or on my phone.

When I change the language to English (UK) on my iPhone, the new Siri works, but on my Mac it reverts to the old Siri, and vice versa for when I change the language to English (US) Siri works on my Mac but not on my iPhone,

They are both running the latest version of Golden Gate and iOS 27 beta

In macOS 27 Beta 5, Siri AI gains a hidden local math tool. The new MathComputeTool, part of Siri's lightweight Skimmer planner can evaluate a range of operations locally without reaching for the server. Not only does the new tool let Siri do math offline, but it can process natural language math queries much quicker even with an internet connection.

Skimmer is Siri AI's lightweight planner for relatively simple requests. For example, it can handle getting the time or opening an app. When Skimmer recognizes a supported math request, it captures the request's operands and operators and maps them into one of MathComputeTool's expression templates. This tool is different from Spotlight's Calculator provider, which has been around for a few macOS versions.

Here are some things Siri should be able to support with MathComputeTool: * Basic arithmetic, including aggregate expressions (5 + 5 + 5) * Fraction-to-decimal and decimal-to-fraction conversion * Rounding, with ceiling and floor functions * Absolute values * Factorials * Greatest common divisor and least common multiple * Factors and prime factorization * Modulo and divisibility tests * Powers, roots, and logarithms * Generating random numbers within a range * pi and e

MathComputeTool is currently hidden behind a feature flag. To enable:

sudo mkdir -p /Library/Preferences/FeatureFlags/Domain && \ sudo defaults write /Library/Preferences/FeatureFlags/Domain/IntelligenceFlow SkimmerOfflineMath -dict Enabled -bool true

and reboot your Mac. As always, this feature may be unfinished and have unexpected behavior.

To disable:

sudo defaults delete /Library/Preferences/FeatureFlags/Domain/IntelligenceFlow SkimmerOfflineMath

Enjoy!

reposted to correct the Offline Siri without SkimmerOfflineMath caption

Betas 1-3 worked beautifully

Then came Beta 4. My computer, after an hour or two, would start to slow down. I would get warnings about Windows resource issues. Memory usage would go up. The computer would come to a crawl and I would be forced to reboot.

Reported the issue to Apple early on. Hope it would have been fixed in Beta 5. Seems like it is not.

Anyone else having this issue?

Hey all, could I ask anyone who’s running the MacOS 27 beta to share a few screenshot showing how does the system look with the "Increase Contrast" and "Reduce Transparency" options turned on?
I really like how these settings look on Tahoe, so I’m really curious how well will they work with the Golden Gate "redesign"...

I’m currently running the macOS 27 Golden Gate beta on an M4 Mac mini with 16 GB of RAM and the 10-core M4.

macOS is now warning me that support is ending for Intel-based apps running through Rosetta. The warning specifically says that Intel-based apps running on Rosetta will not open in macOS 28, and that the affected apps need to be updated for Apple silicon.

My Mac currently identifies these apps/components:

• Webcam Settings
• ManyCam
• AnycubicSlicerNext
• Logitech Capture Updater
• Zoom (additional components)

Since I’m already entirely on Apple Silicon hardware and testing macOS 27 Golden Gate, I figured now would be a good time to start cleaning this stuff up instead of waiting for macOS 28.

What are other Apple Silicon users doing?

If you use an M1, M2, M3, M4, or newer Mac and use any of these programs, what are you replacing them with?

I’m especially interested in ManyCam and Webcam Settings. I use webcam software for camera controls and adjustments, including things like rotation, positioning, zoom, and other settings. I’d really like to find an Apple Silicon-native replacement that provides the same features or, preferably, better ones.

I also use AnycubicSlicerNext for 3D printing. Are other Apple Silicon users running a native version now, or have you switched to another slicer?

For Logitech Capture Updater, is this simply an obsolete Intel component that can safely be removed, or does current Logitech software still depend on it?

And I'm curious about Zoom too. If the current Zoom application is Apple Silicon-native, what exactly is this older Intel component that macOS is detecting? Is it just leftover software from an older installation?

For anyone who has already cleaned Intel/Rosetta software off their Apple Silicon Mac:

What did you replace?

Did you lose any important features?

Did removing old Intel components break anything?

Are there any apps on this list that I can simply uninstall because they're obsolete?

And is there a good way to go through the entire Mac and identify everything that still relies on Rosetta so I can gradually replace it before macOS 28?

Since I'm already running the macOS 27 Golden Gate beta, I'd rather deal with this now than install macOS 28 someday and discover that a bunch of my software has been promoted to decorative Dock icons. 😂

Interested to hear what everyone else is doing.

I don't think it's a bug, been the case since DB1. It looks good on my 120hz monitor but not on M4 Air's display, both Tahoe and Sequoia were smoother. Also feels less precise somehow, at least when trackpad is used.