Thanks! I've also just updated the feedback with further information. This is a regression in iOS 26 and works perfectly fine in iOS 18.

The release notes quoted in the forum post mention that NSManagedObject was annotated with nonisolated, but that does not seem to be the case then? "In beta 5 SDK, CoreData changed several Sendable annotations to resolve compatibility issues with Swift 6’s new MainActor default isolation feature. These changes include marking NSManagedObject as NS_SWIFT_NONISOLATED NS_SWIFT_NONSENDABLE" I have filed a feedback here FB20664344.

Looks like this is fixed in iOS 26.1 beta 2.

That fixes the issue of the cut off bars, but that's not a problem I'm having.

I understand and this is fine. But specifically the behavior of the bottom bar not getting the progressive blur and a fade instead is like that since beta 4 and it that case it would be nice to have official guidance if this is the new intended behavior. This can break a lot of people's layout now that there are no bars any more and when even the progressive blur is gone, it can look ugly when using text and image heavy content. FB19389091

That depends on how broken the database is I would assume. Theoretically they can fix this (or reset the database so that you can at least start anew), but they need to know about this. I've seen reports from two years ago where this happened on other occasions, so this might not be fixed in the near future.

This does the same thing in SwiftUI. You'd need to test if it works on visionOS, though. .toolbarBackgroundVisibility(.hidden, for: .navigationBar)

Except it does not save space. When you drill into a UINavigationController stack, and the title of the controller is different from the tab's title, it will display a double-height nav bar and it looks ugly as hell.