Can we still use @FocusState as designed with Vanilla SwiftUI?

[cohen72]

Hey Guys, We were using 0.3.0 of SwiftUINavigation for a while, but only for specific functionality on NavigationLink. We've been implementing our own @FocusState functionality, setting specific TextField to have focus on the .onAppear of the View. Everything was working until I upgrade to 0.4.2. Now ... even if I don't even import the library and only simply add it as a dependency, our functionality of setting focus no longer works.

I understand there are new APIs around FocusState in 0.4.2, and perhaps now something in the library is overriding this functionality.

Any ideas?

[tgrapperon]

Hey @cohen72! AFAIK, the library doesn't do anything special regarding @FocusState. There is a case study ("Synchronized bindings") where it shows how you can bind a @FocusState to some published field of your model, but this shouldn't affect existing code if you're not already using a .bind view modifier.

One possibility is that some helper shipping with the library is somehow getting selected instead of another one you previously defined internally, but with a different behavior. I would check if one of the new methods/helpers shipping with the app is named similarly to something you defined yourself, especially in an utility module that you import as a dependency too (local definitions should prevail, so I would suspect something defined out of the project). Ideally Swift should warn you if there is some ambiguity, but this is not always the case, for example when the new definition accidentally fulfil some protocol requirement that is defined by default in an extension.

This is probably a long shot, because a glance at pointfreeco/swiftui-navigation@0.3.0...0.4.2 doesn't show obvious new candidates. You can always put breakpoints on all "Binding"s methods and check if one gets called when your focus is broken. The other generic candidates are the .bind modifier, and the internal .didSet binding method.