Hi everyone, I recently updated my Mac to macOS 27 Golden Gate Beta and have encountered a strange issue with window management over a remote connection. Issue: When connected to my Mac via Chrome Remote Desktop (CRD), I can no longer move application windows by dragging their title bars (outer frames). Details: Curiously, I can still drag and move individual tabs within apps (like Chrome or Terminal), which means mouse drag input itself is being transmitted correctly to the OS. This issue only happens when attempting to drag the window title bar/frame over a remote session. Local mouse/trackpad control works perfectly. Everything was working completely fine before the update to macOS 27 Golden Gate Beta. What I've tried so far (with no success): Toggled Accessibility permissions off and on for ChromeRemoteDesktopHost and restarted the Mac. Disallowed and re-allowed Screen Recording permissions. Completely re-installed the Chrome Remote Desktop host application. Disabled "Tile windows by dragging to screen edges" in System Settings to avoid snapping conflicts. It seems like WindowServer or the system-level window management is blocking or ignoring virtual mouse drag inputs specifically on title bars since this beta update. Has anyone else experienced this on macOS 27 Golden Gate Beta, or is there a known API change / security restriction in this version that affects remote input handling for WindowServer? Any insights or workarounds would be greatly appreciated. Thank you!

All of these issues appear when the search controller is set on the view controller's navigationItem and the search controller's searchBar has its scopeButtonTitles set. So far the following issues are affecting my app on iOS/iPadOS 26 as of beta 7: When the scopeBarActivation of UISearchController is set to .onSearchActivation, the preferredSearchBarPlacement of the navigationItem is set to .integratedButton, and the searchBarPlacementAllowsToolbarIntegration is set to false (forcing the search icon to appear in the nav bar), on both iPhones and iPads, the scope buttons never appear. They don't appear when the search is activated. They don't appear when any text is entered into the search bar. FB19771313 I attempted to work around that issue by setting the scopeBarActivation to .manual. I then show the scope bar in the didPresentSearchController delegate method and hide the scope bar in the willDismissSearchController. On an iPhone this works though the display is a bit clunky. On an iPad, the scope bar does appear via the code in didPresentSearchController, but when any scope bar button is tapped, the search controller is dismissed. This happens when the app is horizontally regular. When the app on the iPad is horizontally compact, the buttons work but the search bar's text is not correctly aligned within the search bar. Quite the mess really. I still need to post a bug report for this issue. But if issue 1 above is fixed then I don't need this workaround. When the scopeBarActivation of UISearchController is set to .onSearchActivation, the preferredSearchBarPlacement of the navigationItem is set to .stacked, and the hidesSearchBarWhenScrolling property of the navigationItem is set to false (always show the search bar), and this is all used in a UITableViewController, then upon initial display of the view controller on an iPhone or iPad, you are unable to tap on the first row of the table view except on the very bottom of the row. The currently hidden scope bar is stealing the touches. If you activate and then cancel the search (making the scope bar appear and then disappear) then you are able to tap on the first row as expected. The initially hidden scope bar also bleeds through the first row of the table. It's faint but you can tell it's not quite right. Again, this is resolved by activating and then canceling the search once. FB17888632 When the scopeBarActivation of UISearchController is set to .onSearchActivation, the preferredSearchBarPlacement of the navigationItem is set to integrated or .integratedButton, and the toolbar is shown, then on iPhones (where the search bar/icon appears in the toolbar) the scope buttons appear (at the top of the screen) the first time the search is activated. But if you cancel the search and then activate it again, the search bar never appears a second (or later) time. On an iPad the search bar/icon appears in the nav bar and you end up with the same issue as #1 above. FB17890125 Issues 3 and 4 were reported against beta 1 and still haven't been fixed. But if issue 1 is resolved on iPhone, iPad, and Mac (via Mac Catalyst), then I personally won't be affected by issues 2, 3, or 4 any more (but of course all 4 issues need to be fixed). And by resolved, I mean that the scope bar appears and disappears when it is supposed to each and every time the search is activated and cancelled (not just the first time). The scope bar doesn't interfere with touch events upon initial display of the view controller. And there are no visual glitches no matter what the horizontal size class is on an iPad. I really hope the UIKit team can get these resolved before iOS/iPadOS 26 GM.

ubject: Walkie-Talkie App Not Working After Updating to iOS 27 Developer Version Dear Support Team, I am experiencing an issue with the Walkie-Talkie app after updating my device to the iOS 27 Developer Version. Since the update, the app is not functioning properly, and I am unable to connect or communicate with my contacts using Walkie-Talkie. I have already tried several troubleshooting steps, including restarting the device, checking my network connection, and verifying that both FaceTime and Walkie-Talkie are enabled. However, the issue still persists. Could you please help identify the cause of this problem and advise on any available solutions or known issues related to the iOS 27 Developer Version? Device Model: [IPHONE 17] iOS Version: iOS 27 Developer Version Issue Started: Immediately after updating to iOS 27 Developer Version Thank you for your assistance. I look forward to your response.

I installed the new MacOS Beta 1 on Monday, June 8 and Siri was requested. It is now Thursday, June 11 and I am still on the wait list. The conference is almost over with any interactive sessions. I am concerned that my configuration may be causing a bug. The AppleID I am logged in on the Mac (M4, 24GBs RAM, 512GB storage-130GB free) is not the same as my paid Developer AppleID used to download Xcode, etc. (it is however a Developer ID). This has never been a problem before. Could this be causing an issue? Related question, since I have not gotten the "New Siri" will this actually change the Foundation Models?

Summary While parallel testing Core Location on the new iOS 26.1 beta (23B5044i), I observed what I believe to be a regression of the issue described here: https://developer.apple.com/forums/thread/779192 Specifically, user positioning underground subway stations is noticeably inaccurate on the beta, whereas the same scenarios remain accurate on the unupgraded device below. I work with the MTA (New York City) and work with the OP of that thread. Happy to provide additional testing or details if helpful. Please let me know what else you need. Test Info Riding NYCT from Wall St to 34th St Penn Station on the 2 train carrying two iphones Recording: https://limewire.com/d/dpTWi#pDC3GRYIdE Expected: Consistent underground positioning comparable to prior releases. Actual: Degraded/inaccurate underground positioning on iOS 26.1 beta. Test Devices Left Screen: iPhone 15 Pro Max - iOS 26.1 beta (23B5044i) Right Screen: iPhone 11 - iOS 18.6.2 (22G100) Blue dots show location set by CoreLocation. Red dot on iphone 11 shows the actual location of both devices as I was able to manually place while travelling through a station. Placement through tunnels is not easy to verify and not usually indicated. Timestamps Comparison of when train was actually observed in a station vs when 26.1 and 18.6.2 CoreLocation updated to the station Fulton St 1:48 iOS 26.1 correctly updates (correctly) 2:16 iOS 18.6.2 updates (28sec late) Park Place 4:12 train arrives 4:15 iOS 18.6.2 updates to ~near Park Place 5:04 iOS 18.6.2 updates to Park Place (correctly) 6:07 iOS 26.1 update to ~near Park Place (over 2 mins late) Chambers St 6:02 train arrives / iOS 18.6.2 updates (correctly) 6:14 iOS 26.1 updates to ~near Chambers 6:18 iOS 26.1 update to Chambers (correctly) Franklin St 6:52 train arrives 6:55 iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update Canal St: 7:16 train arrives 7:18 iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update Houston St 7:54 train arrives 8:00 iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update Christopher St 8:37 iOS 26.1 presumably between Houston St and Christopher St 8:40 train arrives / iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update 14 St 9:22 train arrives 9:28 iOS 18.6.2 updates (correctly) 11:01 as train departs station iOS 26.1 updates (1.5 mins late)

It has been 3 days on the waitlist. Is there something wrong with the apple servers?

I just noticed something on macOS 27 beta 1 and I'm not sure if it's a bug or just how the new feature works. After quitting an app with Cmd+Q, the Dock keeps showing the gray dot with the "Running in Background" message. So I checked — ps aux shows nothing running for the app at all. The only trace is its auto-updater job in launchctl list (com.anthropic.claudefordesktop.ShipIt), which is registered but has no PID, so it's not actually executing anything. Out of curiosity I tried Discord and got the exact same thing (com.discord.discord.ShipIt), so this probably happens with any Electron app that uses the Squirrel updater. Is this intended behavior? Trying to understand if the indicator reflects registered background items (and not just live processes) so I know what to expect for Electron-based apps.

I got macOS Golden Gate developer beta, so Xcode stopped working. Then, I got Xcode 27 Beta because I was super excited about it, but then after adding my build, App Store Connect says that I can't add builds made with Xcode beta for review, and since I have macOS Golden Gate, I can't use non-beta Xcode. How do I either archive as non-beta or downgrade in some way (since I can't go back to macOS Tahoe)? I would like to add my app for review soon.

Overview When a project contains SwiftData and the Preview uses a in memory database, SwiftUI preview doesn't show the data Have a look at the ContentView preview Environment Xcode 27.0 beta (27A5194q) 26.5.1 (25F80) Feedback FB23041713 Please can you have a look at the feedback, it also has a sample project and screenshot

Hi, Xcode 27 markdown rendering look fantastic, a big thanks to everyone who contributed to it. Truly such a delight seeing rendered beautifully!! I didn't see it explained in any of the Xcode sessions, if there are WWDC sessions or documentation on this please let me know. Questions Tables get rendered really well, how can I add or remove columns in a table? For links I noticed that I needed to add the link first and then title for the link later, or are there alternate ways?

Hi, On Xcode 27, whenever I create a new Project and select App, an untitled project is created. What is good: When I go on to save the project, the project name uses it to update target name which is nice. Problem: Every time it uses a placeholder team ID, I have to go and manually update the bundle ID and team. This could also lead to unnecessary provisioning profiles created with placeholder IDs. Proposal FB23033844 Xcode to use the last used Bundle ID and Team. This will be similar to how things were in Xcode 26

Hi, On Xcode 27, Device Hub, how to view the simulator with Point Accurate and Pixel Accurate window sizes? These are existing options on Xcode 26 Simulator, so would be nice to have them in Xcode 27 Device Hub. This would be needed sometimes to quickly measure things using a on screen ruler. Feedback FB23033231 If there is no option currently can you please provide options to provide to view Point Accurate and Pixel Accurate window sizes

As the title says, I'd like to run a macOS 27 VM on my Mac (the host is on macOS 26.5.1) in order to test my apps without having to update my host to a beta. My virtualization app of choice (VirtualBuddy) fails on installation when I use the restore image for macOS 27.0 (26A5353q) from the developer website. The developer of VirtualBuddy believes this is a macOS limitation (https://github.com/insidegui/VirtualBuddy/discussions/683). (I filed FB22977958, but I'm not sure if they filed their own bug.) Is there a workaround? It'd be very nice to have access to this during WWDC week. Usually I'd look for device support files on the developer website for download and/or install the Xcode beta first, but I've already installed the Xcode beta and there don't seem to be any device support files available.

After I enabled Enhanced Beta Feedback in Privacy setting, several minutes later when I came back, it was turned off… I don’t know why… This happened many times. Anyone encountered the same issue?

[SKStoreReviewController requestReviewInScene:] no longer displays the review prompt in debug/development builds on iOS 26.5 beta (23F5043k and 23F5043g). According to Apple's documentation, the review prompt should always appear in debug builds to facilitate testing. This was working in previous iOS versions (iOS 26.4 and older). Steps to reproduce: Run app from Xcode in debug configuration on a device running iOS 26.5 beta (23F5043k or 23F5043g) Call [SKStoreReviewController requestReviewInScene:windowScene] with a valid, foreground-active UIWindowScene Observe that the method executes without error (scene is valid per NSLog) but no review prompt appears Expected: Review prompt should display in debug builds Actual: No prompt appears, despite the scene being valid and foreground-active This worked correctly on previous iOS versions (26.4) so looks like this bug was introduced in 26.5 Beta versions. I have already filed a bug report in Feedback Assistant with number: FB22445620

User might be caught in a Guided Access page with error like this when they trying to leave Guided Access. Please pardon me for shotting a photo with phone to show this condition, because I can't even get a screenshot with home button and power key pressed together. I can't lock the screen with power key or by the magnet sensor, can't get back home page with home button. The ways to exit is waiting for the exit button might could use, or the screen shutdown, or enforce the device to shutdown. After exit the Guided Access without rebooting the system, the Guided Access would be freezed for minutes, noticing the Guided Access can't be used. In iPadOS 26, since, I can prove confidently, 26.5beta1 even earlier, could discover that issue. The problem could happen several times in a day. I have raised that issue since April 25th and the ID is FB22608734, which has more than 10 similar reports. To say something beyond the issue, actually I guessed that my device, iPad mini 5th, might can't get the update of iPadOS 27, so I hoped that Apple Developer Teams could at least fix those annoying problems. Actually there is a long list in Chinese with problems summarised by some Chinese User I waited for a long time for a miracle in WWDC 27. But that's a miracle.

After MacOS 26.6 Beta (25G5028f), I see my hard drive constantly filling up in the system data area. It's not local snapshots because I deleted those and they only took up about 20 GB worth of space. This morning, the hard drive was down to only 500MB of space. The odd thing is if I reboot, it goes back to normal and I am back to around 250GB or my 500GB drive. This only started happened in 26.6 Beta, so I am thinking there is an issue with that update?

This started happening on iOS 26.5, and it is still happening after updating to iOS 26.6 beta. The issue is severe enough that my Apple devices are currently not usable for basic communication. I have lost money, time, and thought way too much about this, so I’m really hoping for a resolution. After setting up an iPhone 14 Pro Max on my Apple Account/iCloud, my Contacts, Messages, Phone, and related Apple communication services became essentially nonfunctional. This started after adding the iPhone 14 Pro Max, but it is no longer isolated to that phone. The issue has spread across my Apple devices, including my iPhone 15 Pro Max, iPhone 14 Pro Max, iPad, and Mac. Current Affected devices/apps: iPhone 15 Pro Max iPhone 14 Pro Max iPad Pro Mac Mini M4 Contacts Messages Phone/calls FaceTime or other calling/contact-related services iCloud Contacts / Apple Account syncing The apps themselves become unusable. When I open Contacts, Messages, Phone, or related services, I usually get a blank/white screen, a frozen interface, or a briefly visible cached state. Sometimes I can see old message previews or the previous app state for a split second, especially after force restarting or using the app switcher, but I cannot scroll, select, call, text, or use the interface normally. After about 10 to 15 seconds, the app freezes or crashes. This affects essentially all normal communication functions. I cannot open Contacts. I cannot read or use Messages normally. I cannot place or answer calls. I cannot use my contact list. I cannot use any of my phone numbers or receive verification codes to my phone number. The same failure appears across devices signed into the same Apple Account/iCloud. Contacts still appear to exist on iCloud.com, which makes me think this may be an iCloud Contacts, Apple Account sync, contact-card corruption, or cross-device sync corruption issue rather than simply a local device problem. Troubleshooting already attempted: Updated to iOS 26.6 beta Factory reset the iPhone more than once Tried restoring from backup Tried setting up from zero / fresh setup Tried force restarting Tried resetting SIM/cellular settings Tried setting up with no SIM Confirmed accounts were logged in Confirmed mail/accounts were present and Contacts were enabled where applicable Contacted Apple Support Apple Support escalated the case to a senior engineer Apple Support diagnostics reportedly came back “fine” or “flying colors,” but the devices are still unusable Posted on Apple Support Community, but apple deleted my post and told me to post on the developer forum because I mentioned I updated to iOS 26.6 is beta software.... One possible thing: before this started, I had an AI agent attempt to update my personal contact card with a new phone number. This is an operation that normally goes well, but it was my personal card. I did not verify exactly what it changed. I do not know if this is related, but I am mentioning it because the issue feels like something corrupted in the Apple Account/iCloud contact or identity layer, and somebody in my last thread mentioned emoji or unusual characters might cause this kind of issue. It might have changed my card with some unusual character, field, label, or operation that broke iCloud syncing. Another clue: this started after adding the iPhone 14 Pro Max to my Apple Account/iCloud. After that, the issue began affecting the rest of my Apple devices too. That is why I believe this belongs under iCloud / Apple Account / Contacts syncing rather than only iPhone.

I have received this installation error attempting to upgrade from MacOS 26.4 beta 2 to beta 3 on my Intel 2020 27” iMac, and now trying to install beta 4 from beta 3 on my M1 Max MBP. I have seen from a sprinkling of post that some others have had the same issue. I was able to successfully perform the 2 to 3 upgrade on the iMac in safe boot, suggesting possible compatible, third-party app. But that did not work for beta 4 on either device. I have submitted feedback for each episode. Any others have this issue? Unusual for Apple, I have never had any issues installing beta software before.

I just filed a bug report for the Notes app as follows:Area: Notes Summary: When opening Notes with content that is larger than the open Notes App window, and attempting to edit the note, the entire note content scrolls automatically to the top although the cursor remains where text editing was inserted. Typing on the Smart Keyboard will allow text entry however the note insistently keeps scrolling to the top regardless of how often or how much text is entered into the note. Scrolling the note manually with your touch will stop the action from occurring, however that is intermittent and sometimes will scroll automatically as well. This issue will occur on both iPad and iPhone and regardless of the app is used full screen on the iPad or in Split Screen. When the Notes window is not focused and the user is engaging an app in the other split screen window, the Note window does not scroll, only when it is the focused App. Steps to Reproduce: 1. Open Notes2. Begin to edit the note by scrolling down and selecting text or placing your cursor to enter text.3. More likely to happen with a note which has enough text to enable scrolling of the note.Expected Results: The note body of text should not scroll while editing or entering text and should remain where placed either by scrolling to the place of entry with using touch or with moving the cursor with the direction keys of the Smart Keyboard. Actual Results: The note scrolls on its own without intervention. Version: IOS Beta 10.0(14A5261v) Configuration: iPad Pro 12.9" and iPhone 6S both with iOS beta 10.0