It seems that the binded search text variable is not updated when the value changes outside the SearchBar view. In other words, the search view is not updated with the new @State variable contents.

Not sure if this is has something to do with the multiple Bindings happening between the SearchBar structure and other coordinators classes, etc?

I would like to have it behave like it does in the Settings app on iOS.

Consider the following example:

struct MyView {
    @State var searchText: String = ""
    @State var placeholder: String = "abc"

    var body: some View {
        NavigationView {
            Button("Click me") { self.placeholder = "123" }
                .navigationBarTitle("Test \(placeholder)")
                .navigationBarSearch($searchText, placeholder)
        }
    }
}

One would expect that clicking the button correctly changes both the search placeholder and the title. It, however, only changes the title:

Thus the issue seems to be with the search bar. Digging a little deeper, I found that while the SearchBar initializer is invoked correctly after the state update, no new Coordinator is instantiated, thus leaving it with outdated values.

A possible solution might be to update the coordinator in

I am not sure how idiomatic of a solution that would be though.

Is there a way to have the search bar hidden by default? Currently it just pops in for me and just looks a little jarring. I'm on Xcode 12 beta 3

List(mylist.filter { searchText == "" ? true : $0.name.localizedStandardContains(searchText) }, id: \.id){ item in
            HStack{
                    Text(item.name)
            }
        }
        .navigationBarTitle("Artists")
        .navigationBarSearch(self.$searchText, placeholder: "Find in Artists")

I love how smooth this works when using the list as per your example code, however I am trying to use this with different elements. I have setup an example of where the jumping can occur (ScrollView + VStack).

import SwiftUI
import SwiftlySearch

struct MoviesView: View {
    
    let items: [String] = ["ABC", "DEF", "GHI", "JKL", "MNO", "PQR", "STU", "VWX", "YZ"]
	
    @State
    private var searchText = ""
    
    var body: some View {
        ScrollView {
            VStack {
                ForEach(items.filter { searchText == "" || $0.localizedStandardContains(searchText) }, id: \.self) { item in
                    Text(item)
                }
            }
        }
        .navigationBarTitle("Movies")
        .navigationBarSearch(self.$searchText)
    }

}

Here is a recording of the issue which I hope helps to explain

I am just learning SwiftUI and have no experience with UIKit otherwise I would spend more time trying to fix this myself.
Let me know if you have some ideas and I can do some research and experimentation to help.

EDIT:
I have found this on StackOverflow which demonstrates the exact same issue with UIKit. I am not sure how to implement their solution into this code but I will continue to research.

https://stackoverflow.com/questions/49098249/uitableview-jumps-between-positions-when-activating-and-deactivating-uisearchcon/49156726

Thanks

Hey!

I've added the package to my macOS app that uses SwiftUI as per the instructions in the readme file. I do, however, get error messages when I try to build the application. This is a screenshot of the SwiftlySearch.swift file that shows up when I click on one of the 38 errors that I get:

My project is set to macOS 11.3 as its target. Any idea what is going on?

When using the search bar I get a high CPU usage (100% usage consistently), even when the user has not interacted with the search bar or the app at all. I only tested this on iOS 14.2.1.

Here is an example of how the high CPU usage can be reproduced quite easily:

import SwiftUI
import SwiftlySearch

class SearchViewModel: ObservableObject {
    @Published var searchText = ""
}

struct ContentView: View {
    
    @ObservedObject var viewModel = SearchViewModel()
    
    var body: some View {
        NavigationView {
            List {
                Text("foo")
            }.navigationBarSearch($viewModel.searchText)
        }
    }
}

As soon as the .navigationBarSearch is commented out, the high CPU usage disappears.

Am I doing something wrong here or could this be a bug?