Same thing here; Xcode doesn't see some of the previously downloaded sim runtimes. Also when launching Xcode it's kind of random whether it will see the sim runtimes I do have installed. Whatever the mechanism is for maintaining these things, it's pretty fragile.

The workaround is to download and use the 26.2 simulator for testing. — This ongoing issue is really a pity, because Apple claimed that this would be fixed in Xcode 26.5.

My app is a game whose board layout can make no sense in portrait orientation. I'm willing to make the window resizeable, within limits, but it absolutely must remain in landscape orientation. How am I, and the thousands of developers like me, supposed to cope?

The trouble here, if I may say so, is that Apple has not sufficiently thought this through. There are some apps, perhaps many apps, perhaps very many apps, that rely on a fixed aspect ratio. (Games are the obvious example.) Once established at launch, i.e. by the screen aspect ratio, the window's aspect ratio absolutely needs to remain the same; the app interface cannot make any sense in any other ratio. This is exactly what UIRequiresFullScreen allows us to enforce. With it, my apps do not compel the app to fill the screen on iOS 26, but they do compel the app to maintain the screen's aspect ratio. If Apple wants to take this flag away, they need to provide some other mechanism that does the same job.

Okay, I've worked out workarounds for both problems; see https://stackoverflow.com/a/79921602/341994

"And there is also a problem that when the popover is presented, switching to dark/light mode will not change the appearance" That part is what I came here to complain about. (The system colors being different in a popover does not seem to me to be a bug, because a popover is "elevated" so the colors are different.)

Just to be clear, this has nothing to do with NSStatusItem or LSUIElement. Simply make a new Mac project in Xcode, in Swift, with Storyboard. Run it. You will see the console fill with these warnings.

If you don't want the overflow menu, set the navigation item's style as .browser.

I'm having the exact same issue. I complained about this when this requirement was first promulgated, and here it is happening again. I do not have a new version of any of my apps to submit at this time; does this mean that I cannot update my age ratings now, and that therefore I will never be allowed to update any of my apps ever again??? What in the blue-eyed tunket is going on here????

Sorry for the noise — it turns out that the task ID must begin with the app's bundle ID exactly.

Sorry to barge in on this thread, but I am completely unable to get BGContinuedProcessingTask to work in a UIKit app (the task never starts, the heads-up progress never appears), even though the very same code in a SwiftUI app works just fine. Is this by design? It wasn't mentioned in the video.

I have sent a complaint about this to Apple. The email and the App Store Connect banners specifically say that action is required now, but the new questions, though visible, are not editable so no answers can be provided.

This incident neatly embodies everything that is wrong with feedback reporting to Apple. As a programmer, I regard bug reports from users as a precious gift! Users who provide good bug reports are a valuable resource, to be harbored and treasured. Apple's default response to feedback, on the other hand, is to deny the existence of the issue and to blame and belittle the user who reports it. The user has to repeat the same information many times in order to get Apple to listen at all. When the problem is finally solved, there is no acknowledgment, thanks, or explanation from Apple. The entire process is insulting to the user. This is why I mostly just don't bother any more with the feedback assistant.

@Engineer So far, the "engineering teams" have merely repeated the claim that the app is calling application:didRegisterForRemoteNotificationsWithDeviceToken:. It doesn't. If it did, this would not be a bug!

If you are seeing it, report it to Apple! They aren't going to believe me without support. You can mention FB16995686 in your report but having your own report is what makes the difference.