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?

Did you ever get an answer for this question?

This issue is still present in iOS 16. Did anyone ever find a better solution other than reloading?

Exactly right on both points. Thank you for taking the time to guide me to the solution.

Ok, I got it. Thanks guys! I somehow was under the impression that globally turned on auto-capitalization was a feature that should be working by default on any text entry field.

Unfortunately there was no solution, I'm still running with the try/catch workaround as shown above.

I do have the same issue. It somewhat randomly happens on copy/paste in UITextFields in UITableViewCells. I can also catch it in the debugger and I get the following: *** Assertion failure in -[_UITextKitTextPosition compare:], UITextKitTextViewEditingSupport.m:43. This does seem to be an iOS issue and not an issue in my code. Others have also written about this issue: https://varun04tomar.medium.com/invalid-parameter-not-satisfying-po-crash-on-ios-15-while-pasting-text-onto-uitextview-57e94bbca113 https://stackoverflow.com/questions/69568511/ios15-uitextview-after-dragging-the-view-it-causes-a-crash-invalid-parameter-n Some people are suggesting to implement UITextPasteDelegate to work around the issue. In a large app implementing UITextPasteDelegate on all textfields is very cumbersome and I don't think that this is really the solution to this problem. Has anyone found a better solution for this issue? Will it eventually be fixed in a future iOS update?

Fixed? Not really, rather just “worked around”. Ok, I agree. I’m presume that you chose the latitude property just as an example?  Exactly. Do you have a way to export that DLog to your analytics system? If so, that should be sufficient to tell you which property is causing problems. Yes, I will add some mechanism to have that DLog output sent to me by the users. But that output is not really telling me which property was causing the issue, is it? Its output is just: invalid JSON payload, ignoring (Invalid number value (NaN) in JSON write) Am I missing something?