This is still an issue with iOS/iPadOS 26.2 beta 1. I'm getting comments from users of my app due to this bug that has been around since iOS/iPadOS 26.0 beta 1. Apple, please fix all of the issues related to search scope buttons.

Thanks. I'll adjust my UI for the iPad so the main menu isn't required. In the next day I'll work on filing a bug report about #2. A user can still open a second scene using the "New Window" context menu from the app's icon on the home screen, but a new scene can't be created the old way as I described earlier. And there's no way to know with the current API so it leaves the user wondering what this "useless drag feature" is for.

@Martin81 I get the ReportCrash issue running an iOS 26.1 simulator such as an iPhone 17 Pro. And it is showing a wallpaper. The only sims that don't show a wallpaper in my case are iPad simulators running iPadOS 26.1. But here's what's really weird. I ran the Photos app in the iPhone 17 Pro simulator (which is showing the default wallpaper and causing high CPU). While viewing one of the stock simulator photos I chose "Use as Wallpaper". I went through the steps. Even though the chosen image is now appearing as a black wallpaper, it did fix the high CPU problem for that simulator. Such a strange set of bugs.

There's no macOS-like menu bar when the user chooses "Full Screen Apps". I didn't know this and some of my app's functionality can only be accessed through the main menu bar. So I was thinking I could show some alternative way to access those features when in that mode. iPadOS has supported the ability to open a new scheme through drag and drop using UIDragItem and NSItemProvider and dragging it to the edge of the screen. When a user chooses "Full Screen Apps", this no longer works for opening a new scene. I'd like to disable the drag and drop if it's not going to actually do anything. Those are two main things I can think of so far that depend on the user's choice of multitasking mode.

There is an existing thread on this issue. See https://developer.apple.com/forums/thread/805625

Are all of you posting bug reports with Feedback Assistant? Make sure you do. Be sure your report includes the steps needed to reproduce the issue and include the sysdiagnose attachment. What version of macOS is everyone seeing this issue with? In my case I'm running macOS 26.0.1. I don't know if the version of macOS matters or not. I see the issue with both Xcode 26 and Xcode 26.1. It's just requires starting an iOS/iPadOS 26.1 simulator. I have no issue when running an iOS/iPadOS 26.0 simulator.

This sounds like the issue being discussed here: https://developer.apple.com/forums/thread/803019 This has been fixed in macOS 26.1 which will likely be released today.

@soapbox Make sure you file a bug report using Feedback Assistant.

@jhowlin Make sure you file a bug report using Feedback Assistant. Apple needs to know that more than one person is having this issue.

I've been seeing the same issue for a while now. I have both Xcode 26.0 and Xcode 26.1 beta 3. Running either causes the same issue as soon as I open an iOS/iPadOS 26.1 simulator. I only have a missing wallpaper on iPad simulators with iPadOS 26.1. iPhone simulators show the wallpaper. But either causes the CPU spike due to the ReportCrash process. I can have all of the iOS/iPadOS 26.0 simulators running that I want with no CPU spike. Launch a single iOS/iPadOS 26.1 simulator and in seconds my CPU spikes and stays there. Close that one simulator and everything goes back to normal. I filed FB20868503

Despite what the documentation states, you can actually manually enter a deployment target of iOS 12.0 or later in Xcode 26. If you try to set a deployment target older than iOS 12.0, you get a build message that it only supports iOS 12.0 and later. So yes, you can support iOS 13.0 with Xcode 26. But you will not be able to test on anything older than iOS 15.0. There's no support for simulators before iOS 15.0. And I don't think Xcode 26 will let you connect devices with iOS older than 15.0. The only way to test would be to have actual devices with iOS 13 and 14 and to install the app through Test Flight or Adhoc deployment. But you have to ask yourself why you want to support such old versions. There have been so many API changes since iOS 13. Your code is going to get really complicated with lots of if #available checks. You should seriously consider updating your deployment target to iOS 15 or even iOS 17. Existing users of your app will still be able to use the current version of the app on their older devices. Anyone with newer devices will be able to update to your new version.

All of these are still an issue with iPadOS 26.1 RC

Still an issue with iPadOS 26.1 RC

This appears to be resolved with macOS 26.1 beta 4. Thanks.

When you present a view controller, you can prevent the "swipe down to dismiss" gesture in most cases by setting the presented view controller's isModalInPresentation property to true. Apple even provides a sample app about this: Disabling the pull-down gesture for a sheet