Check out the Migrating to new navigation types article to see how SwiftUI's navigation APIs changed. New in iOS 17 is a modifier that seems to be a replacement for the tag-selection navigation link behaviour: navigationDestination(item:destination:). Something like this could work: var body: some View { NavigationStack { // change here VStack { List(forms, id: \.self) { form in // use new navigation link with a value NavigationLink(value: form) { Text(form) } } // add new modifier .navigationDestination(item: formBinding()) { form in formView(for: form) } } } } private var formBinding() -> Binding<String?> { // remove unused parameter Binding<String?>( get: { selectedForm }, set: { newValue in if newValue != selectedForm { selectedForm = newValue isFormSelected = newValue != nil } } ) }

To get bindings from an Observable class, you need to use the @Bindable property wrapper as normal. However, the bindable value is coming from the environment so this is different. Whether this solution is a workaround or the intention going forward, it works nonetheless. var body: some View { @Bindable var library = library // place in view body List($library.books) { $book in BookView(book: book) } }

Those tutorials were built for Xcode 13.1 (iOS 15) and so aren't updated to use new APIs introduced with later releases, including the new SwiftUI MapKit updates. If you want to proceed with the new APIs, I'd recommend watching these session videos from WWDC23: What's new in SwiftUI Meet MapKit for SwiftUI and having a look at the documentation to see what's changed. Now to convert your "old" code to use the new MapKit APIs. As there is no direct conversion, this was the best I could come up with. struct MapView: View { @State private var region = MKCoordinateRegion() let initialPosition: MapCameraPosition = { let center = CLLocationCoordinate2D(latitude: 34.011_284, longitude: -116.166_860) let span = MKCoordinateSpan(latitudeDelta: 0.2, longitudeDelta: 0.2) let region = MKCoordinateRegion(center: center, span: span) return .region(region) }() var body: some View { Map(initialPosition: initialPosition) .onMapCameraChange(frequency: .continuous) { context in region = context.region } } }

You must remember that we are only in the second beta of SwiftData and there are loads of bugs still floating around at the moment. I just had a quick look at the release notes for beta 2 and look what I found: SwiftData Known Issues • #Predicate does not support UUID, Date, and URL properties. (109539652) So the problem is definitely with the predicate and the fact that you are comparing UUID properties.

You can use this to set the initialX value to the 7th-from-the-end element of the stepDays array. .chartScrollPosition(initialX: stepDays[stepDays.index(stepDays.endIndex, offsetBy: -7, limitedBy: stepDays.startIndex) ?? stepDays.startIndex].weekDay) This also prevents you getting index out of range errors if the length of the array is less than 7.

With iOS 16.4 you now can by using the new presentationBackgroundInteraction(_:) modifier. For your case you can apply this to your presented view: .presentationBackgroundInteraction(.enabled)

The current approach for this would be to move the initialisation of the query to the view's initialiser. Something like this will work: struct ScoreListView: View { @Query private var items: [SWDItem] let selectedPackage: SWDItem init(selectedPackage: SWDItem) { self.selectedPackage = selectedPackage _items = Query(filter: #Predicate<SWDItem> { item in item.package?.id == selectedPackage.id }, sort: \.timestamp) } var body: some View { ... } }

Converting your example code to use the new APIs would look like this: NavigationStack { Button { isNavigating = true } label: { Text("Don't have an account? Sign Up") .foregroundColor(.blue) } .navigationDestination(isPresented: $isNavigating) { SignUpView() } } There is a lot more that can be done with NavigationLink and the navigationDestination modifier so I suggest you look at the documentation to see what else there is. You can also watch the What's new in SwiftUI and The SwiftUI cookbook for navigation session videos from WWDC22 as well as read the Migrating to new navigation types article for more details.

Your code doesn't work because of the way dates are created. Through your extension on Date, you are creating one from a string in the format of "HH:mm:ss" (hours, minutes, seconds). That is all the data the date has in order to be created so other values, such as day, month, year, are filled in from the reference date (00:00:00 UTC on 1 January 2001). In your case, the breakfast date is "01/01/2000 00:00:01". However, the now date has other date components (day, month, year…) provided and so won't be between two dates 23 years ago. With the code you have, you can just change the way you create the now variable like this: var now = Date.parse(Date().dateString()) This extracts the provided components in the format string from the current date using your extensions on Date.

The session video you're referring to is from WWDC23, so it is using the new APIs introduced. The Map struct with the initialiser you are trying to use is only available from iOS 17 and aligned releases. To use these new features you will have to update to Xcode 15. In the meantime, use one of the old (marked as deprecated) initialisers that work in Xcode 14.3.1.

The Foundation framework has built-in support for measurements and conversions. Here are some examples of how you can use the Measurement type and convert between different units: // Yards to Metres let yardsValue = Measurement(value: 50, unit: UnitLength.yards) let metresValue = yardsValue.converted(to: .meters) // Pints to Litres let pintsValue = Measurement(value: 10, unit: UnitVolume.pints) let litresValue = pintsValue.converted(to: .liters) // Pounds to Kilograms let poundsValue = Measurement(value: 100, unit: UnitMass.pounds) let kilogramsValue = poundsValue.converted(to: .kilograms)

While it could be a bug, I think there's another reason. You are attaching the sheet modifier to each button instance, so in your case there could be over 50 sheets ready waiting to be shown. Instead, you could create one sheet and show it when any of the buttons are pressed. Something like this works: struct TestButton: View { @Binding var isPresented: Bool var title: String = "No String" var body: some View { Button { isPresented.toggle() print("tapped") } label: { Text(title) } } } struct TestingBugView: View { @State private var isPresented = false var body: some View { NavigationStack { ScrollView { ScrollView(.horizontal) { LazyHStack { ForEach(1..<55, id: \.self) { num in TestButton(isPresented: $isPresented, title: num.description) } } .padding() .sheet(isPresented: $isPresented) { Text("presented") } } } } } } #Preview { TestingBugView() }

What version of Xcode are you using? I'm assuming you're using Xcode 14+ because NavigationSplitView comes with Xcode's builtin SDKs, in this case with macOS 13. Because your Mac is of a lower version, the API is not available which is what the error is saying.

@Observable should only be used on reference types, or to be more precise classes.

I believe it was mentioned in one of the WWDC activities that Query should support returning a single model object. As SwiftData is in its early stages anyway, the engineers are open to any feedback and enhancement requests. I suggest you file a feedback report detailing why you want Query to return a single model object as well as any useful use cases they can tailor to.