SwiftUI - Placing ToolbarItem on .keyboard does not work

I have a similar issue and haven't found any solution yet. It is obviously a problem with iOS 17 because on iOS 16 it used to work as expected.

Can either of you post some sample code to show the problem? I tested on iOS 17 and iOS 16.4 with this code and saw the same behavior of the keyboard button only showing up for the TextField and not in .searchable, but am unsure if I am replicating it correctly. Either way, this is definitely worth a feedback report (at https://feedbackassistant.apple.com) and please post the FB number here! If you can attach a small sample project to the feedback report, that would help a lot. Thank you!

This is the code I tested with:

struct ContentView: View {
    @State private var text: String = ""
    @State private var searchText: String = ""
    var body: some View {
        NavigationStack {
            TextField("Test TextField", text: $text)
                .toolbar {
                    ToolbarItem(placement: .keyboard) {
                        Button("TestButton") {
                            //code
                        }
                    }
                }
        }
        .searchable(text: $searchText)
    }
}

I have a sample project showing the missing toolbar items on .keyboard placement:

https://github.com/MortenGregersen/KeyboardBarTest

It also contains a video showing the issue.

The issue is also present in apps in the App Store build with Xcode 14.

I have submitted a feedback with all the details: FB13209435

Similar thing is happening in a project im running, but simulator is working fine but on device isnt which is really strange as there the same devices and same software version

I have the same problem. Simulator works as expected and the keyboard button shows, but when I test the build on a device it isn't visible.

If the toolBar is placed in a view that's inside a NavigationStack it doesn't work and this is a bug.

Thanks for all of your responses, this is a known issue with no supported workaround. Please keep filing feedback reports if you have not already, thank you!

There is a workaround! The solution may not for work for everyone but at least it is worth a try. I had to show (and hide) a sheet right after entring the view. Miraculously the toolbar starts to appear after that. Be advised that this code requires iOS 16.4 and above. If you remove .presentationBackground(.clear) it is available for lower targets.

struct YourView: View {
    @State var isShowingAWorkAround = true

     var body: some View{
         HSTack {
         // you code here
         }
         .sheet(isPresented: $isShowingWorkAround) {
             TemporarySheet {
                  self.isShowingAufmass = false
              } resetCallback: {
                  self.isShowingWorkAround = false
              }.presentationBackground(.clear)
           }
      }
}

Code for TemporarySheet

struct TemporarySheet: View {
    let dismissCallback: (() -> Void)
    let resetCallback: (() -> Void)
    var body: some View {
        Text("").onAppear {
            self.dismissCallback()
        }.onDisappear {
            self.resetCallback()
        }
    }
}

Sure you can take anything instead Text("").

Tested on iOS 17.2 public beta (which has identical problem as 17.1).

I have the same issue on iOS 17. The ToolbarItem works on a physical device when debugging through Xcode, but does not work on the physical device.

I have the same issue (IOS 17).

https://gist.github.com/JamesSedlacek/2d0425319e2a854da8c51f4b05c9842a

Here's the workaround I'm using right now.

Experiencing the same issue. Toolbar works fine in simulator, but does not show up on physical device. However, if I open the view, move the app to the background and then move it back to the foreground again, the toolbar suddenly works as expected.

Is your button in an HStack with a Spacer? I used .frame(maxWidth: .infinity, alignment: .trailing) instead and it showed for me.

It's been couple months already and still there is no solution to this problem? Unbelievable!

same problem here