I think I have fixed this, without making any changes to the UINavigationController but to the view body itself. NavigationView { // wrapping in NavigationView SearchBarNavigationView(text: $searchText) { Text(searchText) } content: { Text("Hello, World!") .navigationTitle("Title") } .navigationTitle("Title") // for back button title .navigationBarHidden(true) // hiding bar when showing main content .ignoresSafeArea() Text("No selection") }

I get a lot of this ‘stuff’ in the output terminal but I don’t think they are errors, more just Xcode throwing random comments about constraints and navigation bars.

Home needs to be passed the EnvironmentObject. In ContentView you could add @StateObject private var processStatus = processStatus() and pass this into Home() .environmentObject(processStatus()) // add this

You can use this method to dismiss a keyboard. extension View { func dismissKeyboard() { UIApplication.shared.sendAction(#selector(UIResponder.resignFirstResponder), to: nil, from: nil, for: nil) } } The x in the search bar generally means clear the text, not end editing. You could add an onTapGesture if you’re building the search bar in SwiftUI. It would be helpful to see the code you use to make this CustomSearchBar.

I believe it has, as the pictures are all of Xcode 12 on Big Sur and iOS 14 and I’ve seen some of the new features, such as Map, toolbar and App/Scene in the Landmarks app.

You can apply this modifier to the image .clipShape(ContainerRelativeShape()) to get the desired corner rounding that Apple suggests.

I believe using this results in the correct alignment. extension HorizontalAlignment { private struct CenterLine: AlignmentID { static func defaultValue(in context: ViewDimensions) -> CGFloat { context[HorizontalAlignment.center] } } static let centerLine = Self(CenterLine.self) } Needing to add this to the container VStack(alignment: .centerLine) { ... } and this to the views in the HStacks .alignmentGuide(.centerLine) { $0[.trailing] } // for text label on left .alignmentGuide(.centerLine) { $0[.leading] } // for control on right

I have found that on iPad turning off Enable Results will result in little to no aborts called and the code will run quicker. With the setting on, even if your code is correct (without mistakes or bugs), the complier throws errors and aborts are called.

ProgressView() was introduced to iOS14 but I don’t think that calling you’re own view struct that name is the problem. Try unchecking the Enable Results settings next to the run button. I find that this causes the problem with slow rendering and the Abort called messages, as it does say that it May reduce performance.

If you mean having only one view showing at a time, like on iPhone (not master-detail), then you can use StackNavigationViewStyle(). A navigation view style represented by a view stack that only shows a single top view at a time. Use it like this as a modifier on the NavigationView: NavigationView { ... } .navigationViewStyle(StackNavigationViewStyle())

Yes. The table view will load with the desired style when the view is presented but if the user rotates the device the style doesn't change.

Thanks, that’s really useful. I’m surprised that UICollectionView has a lot of UITableView features and more.

You can add this to your view struct:.onAppear { UITableView.appearance().backgroundView = UIImageView(image: UIImage(named: "imageName")) } It uses a bit of UIKit to change the background view behind the form, not including the rows. The image being passed in to the UIImageView needs to be a UIImage. Take a look at the documentation - https://developer.apple.com/documentation/uikit/uiimage if you need more information on how to configure one.

Xcode 12.4 hasn’t changed this at all. Same message and no on-device preview. 😞 It might be a problem at my end but other people have been having issues so I don’t know what the problem is.

In SwiftUI, not yet. You could implement your own custom trailing sidebar in SwiftUI or integrate some UIKit but that would be quite difficult. You’ll have to wait for WWDC21 for any improvements to SwiftUI.