Thanks @DTS Engineer Quinn, I don't have a spare mac to update and try macOS 26.3 beta, would it be ok if I check once 26.3 is released? Thanks.

@DTS Engineer Thanks a lot Ed! that was spot on, exactly what I wanted. I was breaking my head over this!

The current accepted answer is incorrect so please mark it as unanswered. Please have a look at the feedback FB21436493

This actually is a valid bug, so I have a created a new bug, This is a valid use case Please Apple Engineers, please do have a look at this New Feedback: FB21436493 Also I wish I could deleted my reply to this.

Summary This is not a bug Closed Feedback Concept TabView needs to be the outermost container. NavigationStack should be in the Tab contents. Fixed Code struct ContentView: View { @State private var selectedTab = TabItem.red var body: some View { TabView(selection: $selectedTab) { ForEach(TabItem.allCases, id: \.self) { tab in Tab(tab.rawValue, systemImage: tab.systemImageName, value: tab) { NavigationStack { List { Text(tab.rawValue) } .navigationTitle(selectedTab.rawValue) } } } } } }

See attached Gif

Thanks @j_salling, seems related. I have filed a feedback as well. It would be great to have this fixed at the earliest as possible as it affects production apps.

Following Gif shows the UI glitch

I really hope this gets addressed in #WWDC25. Using a rawValue, you need to hardcode the rawValue, even the below wouldn't compile. #Predicate<Train> { $0.statusRawValue == Status.onTime.rawValue } Error: Key path cannot refer to enum case 'status' If the intent of SwiftData is to be modern and not expose the constraints of SQLite, then more needs to be done to improve support more swift types. Using a #Predicate seems like a blackbox, it works for simple primitive type comparisons but doesn't even work when trying to compare with something like Status.onTime.rawValue

dragDetector returns a GeometryReader which is a View You can look at the documentation for GeometryReader and Color.clear, both of them conform to View. I think it will be best to start simple by going through the basics of SwiftUI. There is great documentation / videos on Apple Developer website. Trying to learn SwiftUI by reading through code might not be the best approach, without the proper understanding of the basics of SwiftUI

Passing a binding in a focusedSceneValue seems to work only when the app uses a WindowGroup. When the app uses a Window (single window) passing the binding in focusedSceneValue doesn't seem to work. When app uses Window focusedValue seems to work. Is this expected behaviour?

Try to replace TrainingAttendanceView with a simple view (example: Color.red) and see what happens. If the sheet opens then the problem could be with TrainingAttendanceView, begin commenting out code till you isolate the problem. If the sheet doesn't open with a simple view then the problem could be in the parent view presenting it. After isolating the problem create a project with minimum code to reproduce the issue and then post it in the forum so that others can have a look.

CoreData Use @FetchRequest to keep CoreData in sync with SwiftUI view https://developer.apple.com/wwdc21/10017?time=581 SwiftData Use Query, to keep SwiftData in sync with your SwiftUI view. Please watch the WWDC videos on SwiftData to see how it is meant to be used with SwiftUI views. Reference: https://developer.apple.com/wwdc23/10154?time=330 https://developer.apple.com/documentation/swiftdata/query https://www.hackingwithswift.com/quick-start/swiftdata/how-to-use-query-to-read-swiftdata-objects-from-swiftui

After updating to macOS 15 Beta 6, I am able to open Xcode 15 Beta 5 and it doesn't crash. You could it try after updating the OS to macOS 15 Beta 6.

For me Xcode 16 beta 5 crashes when I open it on macOS 15 beta 5 Xcode: Xcode 16 beta 5 macOS: macOS 15 beta 5 Thanks for filing the feedback, I hope this gets fixed as Xcode is unusable.