r/MacOSBeta

none of the continuity features work like screen mirroring. The copy paste feature also takes alot of time and not smooth. My devices airdrop is not functional. I recently switched to macbook and was not expecting this. Do you think this is due to mismatch in the versions?

Appreciate your time

Has anyone here installed the macOS 27 beta on their MacBook Air M3?

How has the experience been so far? Have you noticed any bugs, overheating, battery drain, performance issues, app compatibility problems, crashes, or lag?

Does macOS 27 feel smoother or more stable than macOS 26, or would you recommend waiting for a later beta or the official release?

Or It’s just the first time per app? If they send a notification every single time I feel I may just stay in Tahoe (I know I know but I have some software that I have to use)

Has anyone done any measurements on search performance in macOS 27 yet? The only thing I'm finding is that indexing takes a while. Even a subjective telling would be awesome. If you're interested in possible benchmarks to do in both macOS 26 and 27 for comparison, here are some ideas:

• speed to first result of various searches
• speed to full results of various searches
• time to finish indexing
• index size
• CPU or battery usage during indexing
• filesystem watching behavior
• latency after the initial index

I recently woke up and received an out of memory popup, despite none of the apps using any significant RAM. Checked my activity monitor, dasd using 24GB. Nice. After some checking, BiomeAgent (something responsible for Apple Intelligence and Siri/contextual stuff) was repeatedly registering an Apple Intelligence task called com.apple.intelligenceplatform.IntelligencePlatformCore.ViewLive. Because BiomeAgent was registering that ViewLive task over and over, it made dasd accumulate insane RAM usage. Might not happen on all devices. I have an M2 Pro 16GB.

dasd is the Duet Activity Scheduler Daemon, a background system process on macOS that decides when deferred background tasks should actually run.

I already reported this via Feedback, since it's most definitely a beta bug. But if anyone here comes across this issue, here's how to work around this. I mean, it's not clean, this might break Siri or Apple Intelligence features!! (so remember to un-do this workaround once this is fixed), but it works:

Temporary fix

pkill -STOP -x BiomeAgent
sudo pkill -9 -x dasd

dasd should restart by itself and stay small. Mine went from multiple GB back down to around 10 MB.

Undo by restarting.

Persistent fix

mkdir -p ~/bin ~/Library/LaunchAgents ~/Library/Logs

cat > ~/bin/unload-biomeagent-for-dasd.sh <<'EOF'
#!/bin/zsh

sleep 180

uid=$(/usr/bin/id -u)
/bin/launchctl bootout "gui/$uid/com.apple.BiomeAgent" 2>/dev/null || true

exit 0
EOF

chmod +x ~/bin/unload-biomeagent-for-dasd.sh

cat > ~/Library/LaunchAgents/com.$USER.unload-biomeagent-for-dasd.plist <<EOF
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>Label</key>
  <string>com.$USER.unload-biomeagent-for-dasd</string>

  <key>ProgramArguments</key>
  <array>
    <string>$HOME/bin/unload-biomeagent-for-dasd.sh</string>
  </array>

  <key>RunAtLoad</key>
  <true/>

  <key>StandardOutPath</key>
  <string>$HOME/Library/Logs/unload-biomeagent-for-dasd.log</string>

  <key>StandardErrorPath</key>
  <string>$HOME/Library/Logs/unload-biomeagent-for-dasd.err</string>
</dict>
</plist>
EOF

launchctl bootout "gui/$(id -u)" ~/Library/LaunchAgents/com.$USER.unload-biomeagent-for-dasd.plist 2>/dev/null || true
launchctl bootstrap "gui/$(id -u)" ~/Library/LaunchAgents/com.$USER.unload-biomeagent-for-dasd.plist

To verify:

launchctl print "gui/$(id -u)/com.apple.BiomeAgent"
ps -o pid,rss,etime,%mem,%cpu,comm -p "$(pgrep -x dasd | head -1)"

If the workaround is active, launchctl print may say it cannot find com.apple.BiomeAgent, which is expected. dasd memory/CPU should stop climbing.

To undo the persistent workaround:

launchctl bootout "gui/$(id -u)" ~/Library/LaunchAgents/com.$USER.unload-biomeagent-for-dasd.plist 2>/dev/null || true
rm ~/Library/LaunchAgents/com.$USER.unload-biomeagent-for-dasd.plist
rm ~/bin/unload-biomeagent-for-dasd.sh

launchctl bootstrap "gui/$(id -u)" /System/Library/LaunchAgents/com.apple.BiomeAgent.plist 2>/dev/null || true
launchctl kickstart -k "gui/$(id -u)/com.apple.BiomeAgent"

Hope this helps someone that is also experiencing this here! :)

EDIT: I changed the script because the initial one I made for persistent was causing a freeze on boot lol

I thinking of dual-booting my M3 MBA for the public beta. What I would like to do is create a new partition on my internal drive, install the Golden Gate beta, restore my latest Time Machine backup the new partition, then install the new betas there as they come out. Can I have one partition on the beta program without the other partition being on the beta program? Or do people think this is just too complicated an idea. (I've done public betas before, and never had any major issues...just thinking of trying something new.)

I've been running the 26.6 public beta for a little bit now, and I'm noticing some serious input lags with both built in and external keyboard and trackpads.

I've reached out to apple, and each time, they say, "Betas are unstable; uninstall,"; which is fine and understandable, but if it's a public beta, meant for public testing, wth is even the point if they don't take feedback on the potential issues?

I'm trying to figure out what it could be and isolate issues on my own, but the lack of support/feedback is frustrating.

I'm worried it's a hardware issue, but the support team won't even begin to offer assistance until the public beta is completely rolled back, which means a full wipe and restore of my machine, losing at least a few weeks of data.

Since I've updated to MacOS 27 DB 1 & 2 I've noticed that the performance of Safari in basically every kind of website is really worsened. 

I'm surprised because these betas are very polished, and I couldn't notice any other performance drop in other situations.

MacBook Air M1 (8gb ram)

Macbook freezes for 10 seconds when waking up from sleep. Also keyboard sometimes stops working

Has anyone encountered this bugs?

https://preview.redd.it/zfti8dphdyah1.png?width=945&format=png&auto=webp&s=a07136a29d2bacda47602a3a7fe8d8b803a3f47a

this has genuinely driven me crazy
I am on MacOS 27 beta 2 Mac Mini M4

As in the tittle, I have dev beta on my iPad, I am having it mostly for new Siri, I’m curious how it works on MacBook, will I regret updating it? Or wait for public beta? It’s for people who updated their devices to dev beta and can give us a feedback on it 💻

I made the mistake of installing the macOS 27 beta and Xcode 27 beta without keeping a stable environment for App Store submissions. After that, I couldn’t submit updates because Apple requires apps to be built with supported public versions of Xcode.

I didn’t want to restore my Mac or use a second Mac, so I looked for another solution.
Here’s what worked:

I created a private GitHub repository and pushed my project.

I connected the repository to Xcode Cloud in App Store Connect.

I created a workflow in Xcode Cloud.
In the workflow settings, I selected **Xcode 26** and the **macOS Tahoe 26** build environment instead of the beta versions installed on my Mac.

Xcode Cloud built the app on Apple’s servers using those stable versions and submitted it directly to App Store Connect.

Even though my Mac is still running macOS 27 beta and Xcode 27 beta, the build was created with the stable environment in Xcode Cloud, so the submission was accepted.

My app is now **Waiting for Review**.

If you’re in the same situation, this may save you from having to restore your Mac, borrow a second Mac, or wait until the public release of macOS 27.