There is something called the MatchMaker ViewController. Your app should open this up - that's where your list of open matches lives. True. I can get it to show up by enabling showExistingMatches. But what about the initial invitation when the recipient doesn't have the game installed?

Thanks for your reply. The GKMatchmakingMode doesn't have any effect on the GKTurnBasedMatchmakerViewController that I'm asking about. No matter which matchmakingMode is set, it always presents the same set of options (automatch, invite, nearby). Also, unfortunately, this single sentence documentation that you're referring to doesn't explain how it's working. What exactly is a player "actively looking for a match"?

Maybe this is related, I'm not sure: I just discovered that while the leaderboard sets are in status "Live", the individual leaderboards inside the sets are "Prepare for Submission". However, everything was live and approved previously. I didn't change a single bit on the leaderboard configuration. How can this happen? By the way, the achievements are not affected. Just the leaderboards inside the sets.

I have the same issue. What I do is just call fetchSavedGames twice if the first call returns an empty list, and that seems to work pretty reliably.

This is still the case in 2025. I need to call fetchSavedGames twice after a fresh install.

I solved it using this workaround: override func scrollViewDidScroll(_ scrollView: UIScrollView) { guard let tableView = scrollView as? UITableView else { return } for cell in tableView.visibleCells { let rect = tableView.convert(cell.frame, to: tableView) if rect.origin.y <= tableView.contentOffset.y { cell.isHidden = true } else { cell.isHidden = false } } }

Yes, I can confirm that - I've tried it with all the current versions. Unfortunately I haven't found a good workaround for this issue yet.

This is what it looks like in iOS 26 beta 4. The toolbar is behind the tabbar: All I did in this demo project is embed the default view controller in a navigation controller and then embed that in a tabbar. Here's the view controllers code: override func viewDidLoad() { super.viewDidLoad() title = "Hello World" let actionButton = UIBarButtonItem(title: "This is a button on the toolbar", style: .plain, target: self, action: #selector(buttonTapped)) self.navigationController?.isToolbarHidden = false self.toolbarItems = [actionButton]; }

I get an error when trying to update the post, therefore I add it as a new comment: The toolbar is showing up on iPadOS 26.

Specifically, I also wonder how games are supposed to handle this?

I do have the same issue, UIRequiresFullScreen does not seem to be working any more. Also adding UIDesignRequiresCompatibility does not help with that. I understand that many apps are great when supporting all orientations and sizes, but there are also legitimate specific use cases where fullscreen portrait only is all that is needed and wanted.

Also, I do not really understand why this solution is working at all? Why does implementing that delegate call enable the swipe down to dismiss? Did you find it out by accident?

It seems to me that, no matter which of the two variants posted above I'm using, the very first presentation does not look smooth. On the very first presentation I briefly get a white screen (when using the empty UIView) or a transparent screen (when using controller.view) before the presentation.

It's fixed in iOS 18 Beta 5.

Did anyone ever find a solution for this? I'd like to present a UIMenu from a UIView as a result of a gesture recognizer firing... is that possible?