Can you attach an image of what this would look like?

This seems like a trivial problem with a simple solution but the way SwiftUI handles the animation and the repeatForever(_:autoreverses:) method makes it more effortful. The `repeatCount a parameter requires an odd number to prevent the strange “jumps”, and using either of the values 1 and 3 result in no fix. The solution I found was to create two separate animations, one delayed after the other. withAnimation { isAnimated = true withAnimation(.default.delay(0.4)) { // play with delay to see what feels right isAnimated = false } }

Why can't you add the ObservableObject protocol conformance? It only really affects the properties that are marked with the @Published property wrapper, i.e. the properties that update the UI. This is what allows SwiftUI to update the UI based on properties in a class – it is the recommended way. class BoolWrapper: ObservableObject { @Published var value = false {     didSet {       print("Value changed to \(value)")     }   } } struct ContentView: View { @StateObject private var boolWrapper = BoolWrapper()   var body: some View {     Toggle("Toggle", isOn: $boolWrapper.value)   } } The UI can't update if it doesn't watch for changes from inside a class. That is why ObservableObject exists in SwiftUI. If it was a struct, you would only need to use an @State property due to the nature of structs (vs classes).

Thank you for mentioning that. I guess a different approach to this would be storing the boolean value as a local @State variable and manually changing this. Something like this will work: @State private var boolValue = false init() {     _boolValue = State(initialValue: boolWrapper.value) } var body: some View {     Toggle(boolValue ? "Toggle On" : "Toggle Off", isOn: $boolValue)         .onChange(of: boolValue) { newValue in             boolWrapper.value = newValue         } }

You have provided to the Picker the selectOption array as its available selection values. You have set the initial selection value to be an empty string which is not in the selectOption array. You need to specify an initial value that is in the array for the console message to go away. @State var fieldValue: String = "1" // any of the values in selectOption You can also set the selection binding to be an optional string, but then you will get this console message: Picker: the selection "nil" is invalid and does not have an associated tag, this will give undefined results.

There is currently no modifier to do this. SwiftUI doesn't have much in the way of customising list row accessories (I have previously filed feedback for this). The easiest way to get around this would be to use a Button instead and manually perform the navigation; the APIs in iOS 16 make this much easier. For example: @State private var path = NavigationPath() NavigationStack(path: $path) { List(newsList) { article in    Button { path.append(article) } label: {        NewsCell(news: article)    } } .navigationDestination(for: Article.self) { article in NewsLetterView(news: article) } } There are some other hacky workarounds that you can find doing an online search, so you can go with that as well until a new modifier is released (iOS 17?).

It's quite difficult to understand what is happening if you don't, at least, provide some code alongside your explanation. It then wouldn't require us to guess what your current situation looks like. Here's something that works using example data (according to my interpretation of your question): struct ContentView: View {     @State private var path: [Int] = []     @State private var showingSheet = false     var body: some View { // use the path of the NavigationStack to allow for programmatic navigation         NavigationStack(path: $path) {             Text("Hello, World!")                 .navigationDestination(for: Int.self) { num in                     Text("Detail \(num)")                 }             .toolbar {                 Button("Search") {                     showingSheet = true                 }             }             .sheet(isPresented: $showingSheet) {                 SearchView(path: $path)             }         }     } } struct SearchView: View {     @Environment(\.dismiss) private var dismiss     @Binding var path: [Int]     var body: some View {         List(1...10, id: \.self) { num in             Button("Option \(num)") { // dismiss the sheet and then navigate to the selection's corresponding detail view                 dismiss()                 path.append(num)             }         }     } }

The WeatherKit API only needs you to provide a CLLocation object, nothing about the name of a city/country. You will have to use your own list of city/country names and get the locations of these to pass to WeatherKit. Helpfully, CLGeocoder has that functionality already. Here is an example of how to use it: func location(for address: String) async throws -> CLLocation? {     let placemarks = try await CLGeocoder().geocodeAddressString(address)     return placemarks.first?.location } if let londonLocation = try? await location(for: "London") {     // pass londonLocation to WeatherKit     let coordinates = londonLocation.coordinate     print(coordinates) // CLLocationCoordinate2D(latitude: 51.5033466, longitude: -0.0793965) }

Could you not just create a new empty app and then copy over all of the files and settings?

Why is there no toggle button above? What do you mean by "toggle button"? Do you mean the button that hides and shows the sidebar? This is only present when the horizontalSizeClass is .regular. On an iPhone in portrait mode, it won't appear. ‎  And why is the menu always showing? What "menu" are you talking about? ‎ I cant see the detiail view anymore If you want to see the detail view, you need to select an item from the list. As I said before, the two-column layout with the sidebar toggle button is only present when the horizontalSizeClass is .regular. In your screenshot (an iPhone in portrait mode) the NavigationSplitView collapses down to a single column layout and acts more like a NavigationStack.

Could you not just do this: // unwrap variable normally if let nonOptional = optional_ { // create new binding using unwrapped value let binding = Binding { nonOptional } set: { optional_ = $0 } ChildView(nonOptional: binding) ... }

You can use the Spacer() view which will take up all available space. It will also share this space equally when there are multiple. VStack { ViewA() Spacer() // push ViewA to the top ViewB() // takes up the available space Spacer() // push ViewC to the bottom ViewC() } You could also give ViewB a fixed height but I guess you don't want to do that.

Click on the little arrow next to "Supports multiple windows", or go to the "Info" tab, and you will see a small property list table Expand the row that says "Application Scene Manifest" Inside you will see the key "Enable Multiple Windows" Set the value for this to YES (the default) If any of these keys are not there, you will have to add them yourself. I don't know if the checkbox was removed intentionally or not, but it does seem a little strange.

There is a modifier called listItemTint(_:) that seems like it should do what you are asking for. It's worth checking out, but I believe the behaviour changed in iOS 15 for some reason, intentionally or not.

There are three subclasses of MKMapConfiguration: MKStandardMapConfiguration MKHybridMapConfiguration MKImageryMapConfiguration Here are some example conversions from MKMapType to MKMapConfiguration: // MKMapType.standard MKStandardMapConfiguration(elevationStyle: .flat) // MKMapType.satellite MKImageryMapConfiguration(elevationStyle: .flat) // MKMapType.hybrid MKHybridMapConfiguration(elevationStyle: .flat) // MKMapType.satelliteFlyover MKImageryMapConfiguration(elevationStyle: .realistic) // MKMapType.hybridFlyover MKHybridMapConfiguration(elevationStyle: .realistic) // MKMapType.mutedStandard MKStandardMapConfiguration(emphasisStyle: .muted)