Juli Clover:
The release candidate is the final version of macOS Golden Gate that developers and beta testers will get before the software sees a public launch.
Joe Rossignol (Reddit):
Apple this week announced that macOS 27, also known as macOS Golden Gate, will be released to all users with a compatible Mac on Monday, September 14.
iOS 27, iPadOS 27, watchOS 27, tvOS 27, and visionOS 27 will be released on the same day.
Jeff Johnson:
I would like to note two bugs that I reported during the beta period that remain unfixed in the release candidates, and barring a last minute miraculous reprieve, will remain unfixed in the public releases on Monday. This is disappointing, because I thought the point of the betas was for Apple to fix the bugs found by beta testers. While these two bugs are not destructive—do not involve data loss or security issues, for example—they nonetheless did not exist in iOS 26 and macOS 26, so in this respect, Apple’s updates are making their software worse for users.
[…]
The AppleScript run by the test app requires Automation permission, so macOS shows a permission prompt. […] It actually doesn’t matter whether you select Allow or Don’t Allow! […] Either way, just selecting something in the automation permission prompt seems to trigger the bug, causing macOS to wrongly consider the app to be running in the background.
Paul Kafasis:
Unfortunately, Apple’s forthcoming tvOS 27 and HomePod OS 27 updates contain a critical bug that prevents Apple TVs and HomePods from playing AirPlay streams sent by Airfoil. If your devices update to the OS 27 versions, Airfoil will no longer be able to stream to them.
Ron Elemans:
FB24067183 Changing selection in NSTableView by moving the mouse and holding down left button, does not work anymore[…]
Kevin C:
Font Book has been crashing since beta 4 when resizing the Inspector or Sidebar. This was a further degradation over a related bug in Tahoe. So far it seems specific to Font Book.
Previously:
Airfoil AppleScript Cocoa Font Book Mac macOS 27 Golden Gate Safari Safari Extensions
Craig Hockenberry:
It looks like Xcode 27.1 is needed to test the iPhone Duo resizability - and that hasn’t been uploaded yet.
Jordan Morgan:
Cupertino and Friends™️ dropped six new videos over developing, designing, and crafting great apps for the nascent device:
- Design for iPhone Duo
- Prepare your app for iPhone Duo
- Raise the bar with iPhone Duo
- Strike a pose with adaptive layouts on iPhone Duo
- Leverage multiple displays and scenes on iPhone Duo
- Build a great camera experience for iPhone Duo
Nathan Manceaux-Panot:
In the Duo dev video, they describe how text buttons can’t be moved to the new vertical sidebar, as opposed to icon buttons.
I wonder if that’s one of the reasons Liquid Glass pushed hard for icon buttons, even though these are harder to understand; they make the vertical layout possible at all.
Nico Reese:
Totally confusing to me how the toolbar is ordered completely different between both modes here.
Dennis Oberhoff:
I think the problem with the iPhone Duo for developers is mostly that it does not create any new opportunities in the form of a new market or a new audience.
Previously:
Update (2026-09-17): See also: Accidental Tech Podcast.
Previously:
Update (2026-09-18): Xcode 27.1 Beta (Hacker News) adds support for iPhone Duo, but:
StandBy is unavailable in the iPhone Duo Simulator runtime.
Running and debugging most app extensions is unavailable in the iPhone Duo Simulator runtime.
Update (2026-09-21): Léo Natan:
Apple writing example code in Objective C, in 2026. They are REALLY desperate for developers to support this device.
Natalia Panferova:
On iPhone Duo, navigation controls, toolbar actions, and tabs can move into a shared vertical bar along the edge of the display, leaving more vertical space for content. Apps built with the iOS 27.1 SDK get this adaptation through standard containers such as NavigationStack, NavigationSplitView, and TabView. We continue to declare toolbar actions in their usual placements, and SwiftUI determines how to present them in the current context.
Imthaz Ahamed:
I was going through the iPhone Duo specs and realised the inner screen has a different pixel density to the outer screen. The inner 7.6-inch folding display runs at 1878×2670 and 430 ppi, while the outer 5.4-inch display runs at 1398×2034 and 460 ppi.
Jesper:
The iPhone Duo remains interesting, and is clearly a technical tour-de-force that is the outcome of deep thinking about what a foldable phone can be. But the things that sparkle in my mind when I consider it is just the details. They are very important details that yield a noticeably different product, but they are sprinkles on top of a downward slope in user interface design at Apple that does not care any longer about what users or developers want. All that's important is for this year's device to uproot fundamentals and demand that everyone conform to an arbitrary new intuition.
Update (2026-09-29): Craig Hockenberry:
I don’t remember seeing this mentioned anywhere, but you have to be careful about where you place your safe area constraints.
My first pass moved the constraints on scroll/collection views from the superview leading/trailing to the safe area leading/trailing.
[…]
But if you look at Settings and Safari - our only two examples of “what’s right”, you’ll see the scroll indicators are “outside” the navigation bar and hug the edge of the device bezel.
Design iOS iOS 27 iPhone Duo Liquid Glass Programming Simulator Xcode
