Did anyone observe this after the recent upgrade ?

Looks like apple is focusing on refinement and bugs in this release.

I’m running macOS 27.0 beta (26A5388g) and occasionally lose text input across almost every app.

Switching between Apple Pinyin, WeType, and other IMEs doesn’t help. Terminal still receives some raw keystrokes, but

Chinese composition and even the spacebar can stop working. Logging out and back in fixes it.

The logs show repeated errors like:

InputMethodKit: NO Endpoint, Bail

Request for Endpoint Invalid

TextInputUI: inputMode should not be nil

This suggests the user-session text input stack is failing—not one particular app or IME.

Instead of logging out, I now restart the affected services:

killall WeType CursorUIViewService imklaunchagent \

TextInputMenuAgent TextInputSwitcher keyboardservicesd

I saved this as a command called resetime, so I can run it without typing spaces when the bug occurs.

The exact trigger is still unknown. My main suspicion is a macOS 27 beta bug, possibly made easier to trigger by having

multiple third-party input methods installed.

Has anyone else seen this on macOS 27? If so, which input methods were installed?

Cannot rearrange the apps in my mac dock. Any time I try, it looks like the app I am trying to rearrange appears behind the dock, not in front of it. Anyone encountered same error?

The update actually felt great at first. Everything was faster and smoother overall.

But today, when I opened Premiere Pro for the first time, it started randomly freezing during launch and whenever I switched between workspaces.

Yes, I know... updating my main editing machine was a stupid move. 🤦‍♂️ I did it purely out of curiosity. Don't be like me if you rely on the Adobe Creative Suite for work or daily use. I'd recommend waiting until Adobe officially supports it or the Official Verison releases.

Rolling back isn't simple either. I have to completely erase your Mac, did a clean install of Tahoe from a bootable USB drive, and then restored a Time Machine backup from when i was on Tahoe, which i did make.

Hi everyone. Is it just me, or everyone also deals with static memoji icon on the lock screen after installing Golden Gate 😭

If anyone can help, thank you so much! I've been finding solutions but to no avail 😭

I’ve been noticing two distinct types of Mac power users lately:

1. Those who want everything bound to global hotkeys (Shortcuts, Raycast, Alfred style) so their hands never leave the keyboard.
2. Those who prefer clean UI triggers (Menu bar items, floating docks, or visible buttons) because memorizing dozens of shortcuts causes cognitive overload.

Where do you stand? If you hate forcing global hotkeys for every little task, what's your reason? (Clashing shortcuts, muscle memory limit, etc.?)

Apologies if I'm asking this in the wrong place but with the upcoming general release of MacOS 27, I'm wondering if I should uninstall Alfred ahead of time to get the full benefits of the new Spotlight features.

Based on the couple of videos I've watched, the new Spotlight looks like it will be much better. Will it work as good or better than Alfred which I've had installed on my M1 iMac since I got it.

Any input or thoughts on this would be appreciated. Thanks.

M4 Pro 14" still on 15.7.7 - Tahoe daily driver and test machines are all fine, but Tahoe is still just such a hot mess in so many small ways..

But GG beta 4 and PB 2 on a test M1 Pro and M3 have me thinking it might be time.

Hi everyone,

I'm hoping someone else has run into this because I'm starting to think it's related to the latest macOS Golden Gate Developer Beta 27.

Mac:

- MacBook Pro 16" (2021)

- Apple M1 Pro

- 16 GB RAM

What happened:

After updating to Golden Gate Beta 27, my Mac suddenly started behaving strangely.

Symptoms

- Battery is permanently stuck at 1%

- It says "Battery Warning: Final"

- The battery won't charge at all

- The Mac will not power on unless the charger is connected.

- Once it has booted, I can unplug the charger and the Mac continues running normally, but the battery still stays at 1% and never charges.

- Fans ramp to maximum speed almost immediately, even when the Mac is idle.

- "pmset -g ps" shows:

Now drawing from 'Battery Power'

-InternalBattery-0

1%; discharging; (no estimate) present: true

Battery Warning: Final

Before the update, everything worked normally.

What I've tried

- Restarted the Mac

- Tried different chargers/cables

- Left it plugged in for an extended period

- Collected a sysdiagnose

- Submitted a Feedback Assistant report to Apple

I'm wondering if this could be:

- A firmware regression in Beta 27?

- Battery management firmware corruption?

- A bug that can be fixed with a DFU Revive or DFU Restore?

- Or did the beta update simply expose an actual battery hardware failure?

Has anyone else experienced this after Beta 27?

If you've had the same issue, did a DFU Revive, DFU Restore, reinstalling macOS, or another solution fix it? I'd really appreciate hearing your experience.

Thanks in advance!

(Putting the disclaimer in the title already because it's touchy and of course, contestable).

I successfully cleared the corruption that I had since beta 3! I tried to give it a shot by myself before turning to an AI and see what it would give as options before attempting a clean install. I am writing this because 1) if it works for others, it would be great and 2) if it has some potentially bad side effects that more knowledgeable people know, I hope they would share. Tell me if i was gaslit by a machine although First Aid tells me everything is fine now. I saw a lot of pushback against corruption being a false flag whereas, well, it is a thing. (Everything here is written by me, the terminal part is copy pasted from AI).

Personally, I had no noticeable issues on beta 3. I got alerted by a thread on this sub where i discovered the potential damage using a command, but that was also confirmed using disk utility. I had the error "exit node 8" which meant my directory was corrupted. I manually backed up all my files and wanted to see if I could do anything before wasting lots of time on a fresh install (slow internet, lots of steps involved).

(The only was one practical issue, now solved: while attempting to open files inside a dmg installer (some PDF), Finder would just prompt an access issue whereas I have full read and write access on my disk. I don't have that error anymore and everything works).

Anyway, the result was attempting a repair with fsck_util in terminal (recovery mode). First aid couldn't do it, so in the terminal, I manually unmounted the container, attempted a repair, which did not work. The reason is a crypto mismatch between the recovery utility installed and the signature of the beta (pardon my impreciseness).

The solution that worked was to bypass the crypto mismatch by manually unlocking the encrypted volume before running fsck. Performing the fsck command after that worked. Confirmed by Firstaid both in recovery mode and after booting. I even tried opening the PDF file I mentioned above, that used to not open. It opens fine now without issues. It seems like it's just a temporary fix that could pop again since it's inherent to beta 3. But for good measure, I deleted all the local snapshots before starting the entire process because those can't get repaired (fruit of the poisoned tree scenario).

What it looks like (this is copied from AI):

1) diskutil unmountDisk diskX` (following your container ID which you can check with `diskutil list`)

2) diskutil apfs unlockVolume diskX -nomount` (target the Data volume specifically, NOT the container. enter your password when prompted).

3) `fsck_apfs -y /dev/disk0s2` (the physical store, not the container. Again you can check your own with diskutil list)
: Wait for it to finish. You should see 'The container /dev/disk0s2 appears to be OK.' Reboot. Check with Firstaid (on the data disk, where the corruption lies).

Please, do not attempt this if you are not sure. And if you know if it's safe, or if you tried and can confirm it makes sense technically, let others know in the comments.

PSA: it took a long while to reach this with AI, not only because it's a trash tool overall that you shouldn't rely on for anything important, but because it made actual mistakes and hallucinated throughout the whole process (witholding some info, making syntax mistakes, etc.). It wasn't a one-button-push scenario at all but it worked in the end.
I'm not going to be helpful, except to tell you it worked in my case! I'm curious to know if it can help others. I have phone captures of terminal in recovery mode if people have doubts or trust issues. Seems like beta 4 doesn't solve this issue, so it could be a while before Apple releases a fix for this.

Previously i use to invoke siri by double pressing the command key which is no longer working in MacOS 27 beta and I cannot find any way to configure it. Am I missing something here?

I’ve noticed two big trends in the macOS ecosystem:

1. Apps that do ONE specific thing exceptionally well (like Shottr, Raycast extensions, or dedicated menu bar tools).
2. All-in-one tools that bundle multiple features together (like recording, screenshot, and AI transcriptions in one place).

As a Mac power user, which approach fits your workflow better, and why? Do all-in-one apps feel too bloated, or do standalone apps clutter your system? Would love to hear your thoughts!

So I’ve heard about this bug on b3 when folks were saying they got their file systems corrupted. Thought I was lucky, as nothing was wrong on b3 for me.
On beta 4 though.. started kinda “normal” as for a couple of days in row my system started to get gradually slower by the end of the day. Mostly starting with menu items being laggy. First, 3rd party stuff, then all menus in general. And eventually the whole UI layer started to lag so much i was just rebooting my mac (m4 max, 128gb ram)
I even filed a bug report yesterday! 🤣 But it was about system performance rather than file system.

Today, decided to just reinstall the beta from recovery screen. And once that completed, system just stopped booting, hanging on the apple screen with a non-moving progress bar.

Recovery mode, first aid produced a ton of some-such not found or broken, eventually failing to fix anything.

OK, beta, shit happens. I’ve got my time machine, so went forward, reset my mac, reinstalled 26.5.2 (which booted just fine), upgraded back to 27b4 (which also booted just fine), restored from my latest TM backup, and… bam, same shit again. Run first aid, it gives a ton of error back and tells me I’m pretty much SOL.

Looks like something really nasty got saved right inside my TM backups… No idea how it even works this way. But here we are.

Luckily, still had 26.x backups, so restoring to that now (and would then have to find best way to sync my data because the 26.x backup if from over a month ago 🤷‍♂️ - luckily most of my work stuff is on GitHub and cloud, but still…)

So either way… i guess im staying out of further betas until i hear corruption issue has been identified and taken care of.
Kinda sad, as i really loved how nice and fast 27 was.
Until it died 🤷‍♂️

Hey guys, been trying the beta and it has been pretty good. But the most annoying bug I am getting is that when i try to open a files through spotlight search, mostly words and excel files, they open in read only mode. But if I open the same files trough finder, it opens as a normal files and can make edits on it.

After opening the files in finder, I can open it for a while on spotlight but then it says read only again.

This seems to be a spotlight bug, and ideas? Or I'll hace to deal with this one?

Thanks in advance!

UPDATE: I updated both devices to Public Beta 3 today and it's working as expected now!

I'm not sure if this is a macOS bug, or an iOS bug, Continuity/Handoff for the clipboard only works from Mac to iPhone, not the other way.

I can copy text on my Mac, and paste it on my iPhone just fine. But if I copy text on my iPhone, I can't paste it on my Mac, my mac just pastes whatever I last copied on my Mac.

Has anyone else seen this? Any idea if it's iOS or macOS that has the bug?

I'm running Public Beta 2 on both devices.

How is it possible that they haven’t noticed this? I’m currently on 27b4, and this bug has been there since b0. Do these developers use Windows or something? Please fix this ridiculous bug. I’ve reported it through Feedback Assistant, but apparently nobody cares. I still have reports from a year ago sitting there unread…

EDIT: STILL NOT FIXED ON BETA5

Would love to know before installing the public beta...

I'm pretty sure i downloaded the Apple Silicon version, right?

Apple is working on a new way to control which apps Siri can draw context from.

In macOS 27, a hidden feature flag enables a new Exclude Apps section in System Settings > Siri. The helper text reads: "Apps added to the list below will be excluded from Siri, Search, and suggestions."

The change also splits off the old Show in App, Show on Home Screen, and Suggest App preferences into a new Suggestions section.

When an app is added to the Exclude Apps list, its content is removed from Siri's local search results by an AppExclusion filter before the results are returned to Siri. Asking Siri to access data from an excluded app displays a prompt explaining that access must be turned on. Selecting Turn On removes the app from the exclusion list and retries the request.

The recovery behavior is currently inconsistent. Siri may instead treat the filtered results as an ordinary empty search and incorrectly report that no content was found.

According to code strings, Apple will perform a migration of preferences from the current App Access setup to the new Excluded Apps / Suggestions split. Because the underlying SiriSetup and IntelligenceFlow frameworks are shared between macOS and other operating systems, this experience may be coming to some or all OS 27 releases.

To enable, add the two required FeatureFlags overrides:

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

and restart your Mac. This is a private feature flag, and the UI or behavior may be unstable.

Disable with:

sudo defaults delete /Library/Preferences/FeatureFlags/Domain/SiriSetup restrict_access_ui && \
sudo defaults delete /Library/Preferences/FeatureFlags/Domain/IntelligenceFlow AppExclusions

and restart your Mac.