.bottomBar toolbar item missing after rotation in NavigationSplitView on iOS 26 (Regular width / compact height)

A ToolbarItem(placement: .bottomBar) inside a NavigationSplitView detail/destination view is missing after a device rotation on iOS 26. The bottom toolbar is missing until the view has been presented in both orientations, after which it renders correctly from then on. The issue does not reproduce on iOS 18.

Environment

  • iOS 26 only — does not reproduce on iOS 18
  • iPhone 17 Pro Max and iPhone 17 Air (i.e. devices that expose the landscape size class Regular width / compact height)
  • SwiftUI NavigationSplitView with .balanced style

Steps to reproduce

  1. Run the sample below on an iPhone 17 Pro Max or Air (or a simulator of either).
  2. Open the detail view (which contains a .bottomBar toolbar item) while the device is in either orientation.
  3. Rotate the device.
  4. Observe that the bottom toolbar is now missing.

Expected behavior

The .bottomBar button remains visible across rotation, regardless of which orientation the view was first presented in.

Actual behavior

  • On first presentation, rotating the device causes the bottom toolbar to disappear.
  • Once the view has been presented in both landscape and portrait (roughly the third presentation), the bottom bar renders correctly and continues to behave correctly afterward.
  • The behavior is inconsistent


import SwiftUI

@main
struct MinimumReproducibleEventApp: App {
    var body: some Scene {
        WindowGroup {
            NavigationSplitView(columnVisibility: .constant(.all)) {
                NavigationLink("Primary") {
                    ContentView()
                }
            } detail: {
                Text("Hello")
            }
            .navigationSplitViewStyle(.balanced)
           
        }
    }
}


ContentView


import SwiftUI

struct ContentView: View {
    var body: some View {
        VStack {
            Image(systemName: "globe")
                .imageScale(.large)
                .foregroundStyle(.tint)
            Text("Hello, world!")
        }
        .toolbar {
            ToolbarItem(placement: .bottomBar) {
                Button("Hello") {
                    print("hello")
                }
            }
        }
    }
}

Thanks for the post, are you using Xcode 26.5? I just copy and paste your code and I don't see what you are seeing:

Instead of relying on the native .bottomBar placement (which is susceptible to these navigation bridging bugs), you can build a custom bottom bar using .safeAreaInset. This guarantees the bar stays pinned and visible across all rotations, and you can style it to look identical to the native bottom bar.

Even thought for iOS I use just that:

#if os(iOS)
            ToolbarItem(placement: .bottomBar) {
                Button("Hello") {
                    print("hello")
                }
            }
#elseif os(macOS)
            ToolbarItem(placement: .automatic) {
                Button("Hello") {
                    print("hello")
                }
            }
#endif

But you can always do:

 .safeAreaInset(edge: .bottom) {
            HStack {
                Spacer()
                Button("Hello") {
                    print("hello")
                }
                Spacer()
            }
            .padding()
}

I'm more interested in knowing what Xcode are you reproducing that.

Thanks

Albert
  Worldwide Developer Relations.

I see what about when you set the toolbar to be visible?

.toolbar {
            ToolbarItem(placement: .bottomBar) {
                Button("Hello") {
                    print("hello")
                }
            }

        }.toolbar(.visible, for: .bottomBar)

Albert
  Worldwide Developer Relations.

Hi Albert, I'm on Xcode 26 the latest version but the issue has been ongoing across all the 26 releases.

@chrisw5249 I think is worth a bug and we can look exactly what you are seeing and how that changed.

Can you make sure you upload with the bug a focused sample showing the issue exactly. Thanks so much for your patience while looking at that.

Once you open the bug report, please post the FB number here for my reference.

If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why?

Albert
  Worldwide Developer Relations.

Report opened FB22947031

Thanks @chrisw5249

You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label "Resolution." We're unable to share any updates on specific reports on the forums.

For more details on when you'll see updates to your report, please see What to expect after submission.

Albert
  Worldwide Developer Relations.

I hit this too (iOS 27, NavigationSplitView with .bottomBar items in the sidebar, on a device that changes size class - I tested on an iPhone Duo) and tracked down what’s happening.

When the split view collapses or expands, UIKit moves the column’s hosting controller between two different navigation controllers: the column’s own one, and a separate compact one. The toolbar items move with the hosting controller, but the bar’s visibility (isToolbarHidden) belongs to each navigation controller, and SwiftUI doesn’t re-apply it after the move. So you can end up in a navigation controller whose bar is still hidden, even though your items are there. That’s why hiding/showing the sidebar or pushing/popping brings it back: those make it get set up again.

SwiftUI seems to only re-send toolbar state when its value changes, so a workaround is to make the visibility depend on the horizontal size class:

.toolbarVisibility(horizontalSizeClass == .compact ? .automatic : .visible, for: .bottomBar)

The value changes on every collapse/expand, so it gets sent to whichever navigation controller is showing the column at that moment.

The same thing breaks .matchedTransitionSource on a bottom-bar item (“Starting a zoom transition from a nil view…”). Each navigation controller builds its own bar button, and the source isn’t registered again on the one you move back to. Making the source ID depend on the size class fixes that too.