Environment
Device: iPhone Duo, closed (outer display), iOS 27.2
Xcode 27.1 (27A9275), iOS 27.1 SDK, deployment target iOS 18
SwiftUI app lifecycle (WindowGroup, generated scene manifest, generated UILaunchScreen), not letterboxed
What happens
On the iPhone Duo's outer display, the Game Center screens that GKAccessPoint.trigger(...) opens put their top controls (the round back button at the top left, the "Play" button at the top right) right up in the display's rounded top corners, where the corner partly clips them. The same screens look correct on other iPhones.
The outer display's status sits in a column at the right, so a full-screen window there gets a top safe area inset of 0. On other iPhones the top inset (status bar or Dynamic Island) keeps these buttons clear of the corners. The overlay appears to rely on that inset and has no margin of its own for the display's corner radius.
Our own app content on the same display handles this: when the top safe area is 0 we add a fixed top margin. The Game Center overlay has no API for us to do the same, at least none that we can find.
Steps to reproduce
Sign in to Game Center on an iPhone Duo and keep it closed (outer display).
In any app, call
GKAccessPoint.shared.trigger(leaderboardID: "<id>", playerScope: .global, timeScope: .allTime, handler: {})
Look at the top corners of the Game Center screen, on the leaderboards list and on a single leaderboard.
Expected: the back and Play buttons sit clear of the rounded corners, as on other iPhones.
Actual: they sit under the corners (screenshot, though it doesn't show the camera cutout)
What we tried (none changed the layout at all)
Binding the access point to our window before every trigger:
let scene = UIApplication.shared.connectedScenes.compactMap { $0 as? UIWindowScene }
.first { $0.activationState == .foregroundActive }
if let window = scene?.keyWindow { GKAccessPoint.shared.parentWindow = window }
GKAccessPoint.shared.trigger(leaderboardID: id, playerScope: .global, timeScope: .allTime, handler: {})
Hosting GKGameCenterViewController (deprecated in iOS 26, used only for this test) as a child of our own full-screen view
controller, with a top safe area margin:
final class GameCenterHolder: UIViewController, GKGameCenterControllerDelegate {
let screen: GKGameCenterViewController // GKGameCenterViewController(leaderboardID:playerScope:timeScope:)
// init sets modalPresentationStyle = .fullScreen
override func viewDidLoad() {
super.viewDidLoad()
screen.gameCenterDelegate = self
addChild(screen); view.addSubview(screen.view); screen.didMove(toParent: self)
}
override func viewSafeAreaInsetsDidChange() {
super.viewSafeAreaInsetsDidChange()
screen.additionalSafeAreaInsets.top = view.safeAreaInsets.top < 1 ? 20 : 0
}
nonisolated func gameCenterViewControllerDidFinish(_ vc: GKGameCenterViewController) {
MainActor.assumeIsolated { dismiss(animated: true) }
}
}The screen opened and worked, but its layout was identical.
The same holder, giving the child a smaller frame instead (starting 20 pt lower):
override func viewDidLayoutSubviews() {
super.viewDidLayoutSubviews()
let top: CGFloat = view.safeAreaInsets.top < 1 ? 20 : 0
screen.view.frame = view.bounds.inset(by: UIEdgeInsets(top: top, left: 0, bottom: 0, right: 0))
}Still identical, so the screen seems to be drawn by the system outside the app's view hierarchy, out of the app's reach.
We also checked the usual causes: the app is built with the iOS 27.1 SDK, uses the scene lifecycle and a generated launch screen, doesn't use UIScreen.main for layout, and fills the outer display edge to edge (not letterboxed).