Yes, the bug is present with or without UIDesignRequiresCompatibility=TRUE. In fact, the bug is even present in apps compiled with Xcode 16 but running on iOS 26 devices. So, presumably the bug is low level – lower than the iOS 18 compatibility layer. A lot of apps must be hitting this issue!

For me, custom sounds do seem to be working but they do not loop, which effectively makes them useless as an alarm. For now, I've disabled the custom sound feature in my app and I just set the sound to .default. I plan to enable the feature if/when Apple fixes it.

I filed a bug report (FB20465338) but I also want to note some more details here in case this is useful to someone: When navigating back/forward in a WebView or WKWebView, the page suddenly jumps up. The reason appears to be that WebKit automatically adds some padding to the top of the webpage to account for the unsafe nav bar area, but it then forgets to account for this padding when navigating back/forward. The effect is especially pronounced if you swipe back/forward. When swiping you see a static preview of the incoming page, but when you release the swipe, the page suddenly jumps up. As far as I can tell, this has always been an issue, but before iOS 26 it wasn't really a problem because the WebView would usually be flush against a solid nav bar. However, in iOS 26, this bug is problematic because Apple is asking us to flow the web content behind the nav bar; indeed, this is the default behavior of a WebView. There's effectively no good solution in iOS 26 because you basically have two choices: Adopt the default behavior with the content flowing behind the nav bar; but then you get a janky back/forward experience. Set .ignoresSafeArea(.all, edges: .bottom) so that the content does not flow behind the top nav bar, but then the nav bar is plain white/black and it looks bad for the content to just disappear abruptly without some kind of border or fade effect. This can't simply be solved by making the nav bar a different color because then you get into issues with the glass buttons and the floating iPad sidebar. Would love to hear if someone figured out a workaround, even if it's just some styling to make Option 2 less bad.

Yes, I'm having the same problem (with a wrapped WKWebView, but presumably also the new WebView). The jumping-on-back-button issue was also a problem before iOS 26, but you could work around it by using .ignoresSafeArea(.all, edges: .bottom) However, now in iOS 26, Apple wants the content to flow behind the toolbar, meaning the above fix is no longer suitable. Did you manage to find a workaround?

Did anyone manage to solve this issue? Exactly as @jkmazur says: the title text is being rendered under the background color, and it's still broken in beta 9! Here's a minimal example: struct ContentView: View { @State private var path = NavigationPath() var body: some View { NavigationStack(path: $path) { List { Text("Item 1") Text("Item 2") Text("Item 3") } .navigationTitle("Title") .toolbarBackground(Color(red: 0.5, green: 0.5, blue: 0.5), for: .navigationBar) .toolbarBackgroundVisibility(.visible, for: .navigationBar) } } } Expected result: Title is rendered above the gray background. Actual result: Title is rendered below the gray background.

Can you show us your SchemaV1 and SchemaV2, and explain what you're trying to do? It looks to me like you're trying to manually create a SchemaV2.Month and a SchemaV2.Transaction in the willMigrate, which is probably not what you want.