swiftui

iOS 26 Navigation Title Not Displaying - Solution Problem Description After updating to iOS 26 beta, navigation titles stopped displaying in some of our SwiftUI views, while others continued to work. The affected views showed no navigation bar - the title, large title display mode, and toolbar items were not visible. This behavior is different from iOS 18, where the same code displays navigation titles as expected. Affected Configuration iOS Version: iOS 26 beta (all current betas through beta 7) SwiftUI: NavigationStack with .navigationTitle() and .navigationBarTitleDisplayMode(.large) Specific Pattern: Views where ScrollView or Form is the direct child of the view body The Change in Behavior In iOS 26, when a view's body directly returns a ScrollView or Form, the navigation title doesn't appear. Here's an example of code that displays the navigation title in iOS 18 but not in iOS 26: struct DashboardView: View { var body: some View { ScrollView { LazyVStack { // Your content here } } .navi

@DTS Engineer That's great to hear! I'll definitely be on the lookout for OS 26 betas to see if it gets fixed and I'll remove the workarounds that I've added. Do you know if the issue is WebKit related or SwiftUI related? Asking because if it's WebKit, it might be available on the WebKit bug tracker that's publicly available, and rather than needing to check on every beta, I could keep an eye on the bug ticket to see what's the progress! Either way, thanks again for looking into this! Can't wait for it go get fixed, it'll make my app looks so much better! 🤞

Hi team, I found another werid issue in iPad OS 26 only. I can easily reproduce it with a simple example app even in iPadOS 26 RC. I've submitted a feedback FB20215332, could you have a look? Thanks! We have a UITabBarController which contains two tabs. The first tab is a UINavigationController which includes ViewControllerA and ViewControllerB The second tab is just a simple UIViewController ViewControllerC We set the self.traitOverrides.horizontalSizeClass = .compact in TabBarController because we don't want to show the new style of tab bar. We set the hidesBottomBarWhenPushed to true for ViewControllerB when pusing from ViewControllerA because we don't want the tab bar to show in the navigation flow. Also, there is a button in ViewControllerB and it can navigate to ViewControllerC. However, when we tap the button in ViewControllerB, it did navigate to ViewControllerC but the TabBar is missing and at this point we have to kill the app, otherwise we cannot do anything. As I mentioned above, this issue only h

Hi @DTS Engineer I included the exact sample code to reproduce this problem in my original post. It is a self-contained example snipped that can be previewed in Xcode. For reference, let me include it again: import SwiftUI struct TablePreviewContent: Identifiable { var id: Int { text.hashValue } var text: String } #Preview { let content = [TablePreviewContent(text: Hello), TablePreviewContent(text: World)] Table(content) { TableColumn(Title, value: .text) } } Previewing this on iPadOS 26 as well as iPadOS 18.5 within Xcode 26 (Release Candidate, Version 26.0 (17A321)) results in the output I shared in the screenshot above. Please note that this request is regarding SwiftUI.Table and not SwiftUI.List.

Did you find a solution to this? I’m having the same issue. In Notes, for instance, keyboard toolbar buttons have a nice gap between the keyboard and the toolbar. I can’t duplicate this in SwiftUI.

Thank you for sharing your post. I am unable to view your code for the Table and the customization you are implementing. For a simple list, you can utilize the code provided below, which will generate a list on the main body. However, it would be beneficial to observe the specific customization you are making to achieve that behavior. Additionally, could you please provide the Xcode version and beta number you are using? import SwiftUI struct ContentView: View { var body: some View { Text(Title) NavigationStack { List { Text(Hello) Text(World) } } } } #Preview { ContentView() } Resources: https://developer.apple.com/documentation/swiftui/list Albert Pascual
  Worldwide Developer Relations.

On iOS, your app is sandboxed, and hence doesn't have access to a file outside of its app sandbox. When you select the file using UIDocumentPickerViewController (or the SwiftUI counterpart fileImporter), the system automatically extends the app sandbox to the file, which allows the access to your app. From there, your app can grab and save the security-scoped bookmark of the file URL, and use it to access the file next time, without user interaction anymore. See Enabling Security-Scoped Bookmark and URL Access, if needed. The app sandbox is to protect resources and improve the security. There is no way to bypass the protection, and so the answer to your question is no. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Using a UIViewRepresentable like this works, but the Liquid Glass animations for the slider look very wonky and choppy. On slider release there isn't even an animation at all. import SwiftUI import UIKit struct ContentView: View { @State private var sliderValue: Double = 0.48 var body: some View { VStack { VStack { SafeSlider(value: $sliderValue, range: 0...1.18, step: 0.01) Text(Value: (sliderValue, specifier: %.2f)) } .frame(maxWidth: 128) } .padding() } } struct SafeSlider: View where Value.Stride: BinaryFloatingPoint { @Binding var value: Value var range: ClosedRange = 0...1 var step: Value = 0 var onEditingChanged: (Bool) -> Void = { _ in } var body: some View { #if targetEnvironment(macCatalyst) if #available(macOS 26.0, *) { SliderWrapper(value: $value, range: range, step: step, onEditingChanged: onEditingChanged) } else { defaultSlider } #else defaultSlider #endif } private var defaultSlider: some View { Slider(value: $value, in: range, step: Value.Stride(step), onEditingChanged: onEditing

I'm attaching some more information, code and screenshots of the problem on two different devices using iOS 26 23A5336a. The colors are used in SwiftUI View which is passed to the content parameter of AppIntent.requestConfirmation. The colors are loaded using Bundle(named:in:compatibleWith). The structure of the view is (with some stripping) this: struct IntentView: View { var body: some View { VStack(alignment: .leading) { VStack(alignment: .leading) { Text(message) .foregroundColor(.textColorNeutral100) Text(userName) .foregroundColor(.textColorNeutral100) } Text(badgeName) .foregroundColor(.backgroundColorNeutral100) .padding(Constants.smallMargin) .background { Capsule() .fill(Color.backgroundColorPrimary50) } } .scenePadding() } } Correct colors Wrong colors (probably no colors)