Are you referring to UIAlertController? You don't need an anchor. Just create the alert and present it. It will appear in the middle of the screen. Nevermind. I just noticed this is posted in the SwiftUI section. My answer is for UIKit.

It's moved again. In Xcode beta 3 it's now here:

Yeah but that's more awkward than the solution I gave. Typing a ! is easier than adding the #else.

Setting frames and bounds is still supported, even in iOS 26. Constraints have a lot of advantages but they are not required.

Did you find a solution to this? I'm trying to do the same thing. I can't find any delegate methods that would tell you the current height of the sheet as it is being dragged. Constraints might work to position the view above the sheet but that won't help to decide when to show/hide the view as the sheet gets higher or lower.

Please see Opting-out of window resizing in iPadOS 26 and UIRequiresFullScreen in iPadOS 26 for existing discussions on this topic.

This is not the proper place for reporting bugs. Please use the Feedback Assistant app to report any issues to Apple.

I submitted bug FB18883173

See this thread: https://developer.apple.com/forums/thread/789898

The proper way to make such a request is to use Feedback Assistant.

In App Store Connect you create one app. Within that app you setup multiple platforms. Each platform gets its own binary, app description, app screenshots, etc. But all use the same app name. Though I don’t know if you can setup different binaries for iOS and IPadOS. My own app supports both iOS and IPadOS with one binary and then macOS with another.

iOS 26 has a lot of issues like this where it breaks how tinting works. Please file a bug report using the Feedback Assistant app. Apple needs to know that this needs to be fixed.

@DTS Engineer I've filed the following reports related to various tinting issues since beta 1. None have been resolved yet as of beta 4: FB17989300 FB17996063 FB18061370 FB18745302 I do hope these get resolved. Thanks.

This is not the place to report bugs to Apple. Use the Feedback Assistance app to submit a bug report (and attached sample app).

Just to keep people updated, this issue still exists using a macOS 26 beta 4 guest with Xcode 26 beta 4 on a macOS 15.5 host. I'm wondering if updating the host to macOS 15.6 will help resolve this. I'm not yet in a position to try with macOS 15.6 RC but if anyone does, please update.