@pcfist Thanks for the confirmation. I'll give it a try when I get a chance. Unfortunately I am spending most of my time finding and reporting macOS/iPadOS/iOS 26 bugs that are impacting my app. Then I waste time trying to find work arounds since Apple isn't fixing any of the issues.

Change your code in viewDidLoad to: var cfg = PagesInterface.configuration cfg?.cornerStyle = .fixed // Or change the button's "Corner Style" to "Fixed" in the storyboard cfg?.background.cornerRadius = 0 PagesInterface.configuration = cfg With a style of fixed the button's corner radius comes from the background's cornerRadius property. Please also note that it is common practice to name variables starting with lowercase letters. Your PagesInterface variable should be named pagesInterface. Uppercase names are usually used for class/struct/enum names.

@Matt522 Make sure you file a bug report using Feedback Assistant. Apple needs to know that this affects people's apps. Be sure your bug report includes a simple app that demonstrates the issue.

Yeah! It's working! I have a macOS 26.0 host. In UTM I have a macOS 15.7 guest with a Provisioning UUID that has never been added as a device in the developer portal. I also have a macOS 14.6.1 guest that has already been added to the developer portal. In my developer account I added a new device with the new guest VM's UUID. It's the longer style with lowercase hex digits. I then edited my existing manual provisioning profile with the new device. I also added the older existing device that has the short, uppercase style UUID. In Xcode (26.1 beta 2) I changed my app's signing from automatic to manual and referenced the updated provisioning profile. I built the app and copied the new app to a share I use for the VMs. I ran the VMs and tried to run the updated app. It failed. I missed one step that maybe some others might miss. In Xcode, go to Settings, Apple Accounts. Select your account. Then select your team. Then click on "Download Manual Profiles". Once I did that, I rebuilt the app with the now properly updated provisioning profile and recopied the app to the share. And now the app runs in both guest VMs! Key steps for those that are not starting from scratch: Update your provisioning profile in your developer account. You may need to remove devices and then re-add them. Existing devices might only work if the case of the provisioning UUID on the device matches the case shown in your developer account. Be sure you are using the updated provisioning profile when you build. Update via Xcode's Settings screen before building the app. Thanks to those that made this happen.

Like most app metadata in App Store Connect, screenshots can only be updated while you are preparing an app update. So yes, you need to create a new release (and upload a new binary) and update its screenshots before you submit it for review.

All of these issues still exist with iPadOS 26.1 beta 3.

Still unresolved with iPadOS 26.1 beta 3.

This issue still exists in macOS 26.1 beta 3.

Now that this is mostly working, I've come across a new issue I'm wondering if anyone else is seeing. Using UTM version 4.7.4 on a macOS 26.0.1 host, I am setting up a macOS 26.1 beta 3 guest. I am unable to log into my Apple ID in the macOS 26.1 beta host. This happened with beta 1 and now with beta 3. This is not just the normal limitations of logging into an Apple ID in a macOS VM. With macOS 26.1 beta, you can't login at all. This means no iCloud access. This means you can't even update to the next beta since you need iCloud access for the Software Update screen to even offer the Beta Software update option. I also have a macOS 15.7.1 VM and a maCOS 14.6.1 VM on this same host and they both let me login just fine (with the usual limitations). I filed bug FB20668616 but I'm curious if anyone has seen this. One step forward, one step back.

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

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

Still an issue with iPadOS 26.1 RC

All of these are still an issue with iPadOS 26.1 RC

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.

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