column

Xcode 14.0 beta 5 (14A5294e) seem to have fixed my issues with NavigationSplitView Fixed - Warnings Fixed - Selection of cell not happening (2nd time) in compact mode (For 3 column layout) - so no need to set the selected state of the middle column to nil onDisappear Hopefully it has fixed your issues as well, if not please file a feedback

This thread is about provisioning Network Extension providers. That capability is not supported by a free accounts (what Xcode calls a Personal Team). If your goal is to create an NE provider, you’ll need a paid account. For information about which capabilities are supported by which account types, see Developer Account Help > Reference > Supported capabilities (macOS) and the equivalent docs for our other platforms. In this context the Apple Developer column shows the capabilities for a Personal Team. If you’re not trying to create an NE provider, I recommend that you start a new thread with the details of your issue. Oh wait, it looks like you’ve started this thread. I’ll respond over there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

From the way Apple made the NavigationSplitView API, it is clear that having two and three column layouts shouldn't happen or should be avoided. Nevertheless, you can still achieve this through the use of two split views wrapped in a condition. Something like this, which I have tested, will work: struct ContentView: View { @State private var selectedInt: Int? = 1 @State private var columnVisibility: NavigationSplitViewVisibility = .all var sidebarList: some View { List(1...10, id: .self, selection: $selectedInt) { int in NavigationLink(Row (int), value: int) } .navigationTitle(Sidebar) } var contentView: some View { Text(Content (selectedInt ?? 0)) } var detailView: some View { Text(Detail (selectedInt ?? 0)) } var body: some View { Group { // Only rows that are a multiple of 2 will have a two-column layout if selectedInt?.isMultiple(of: 2) == true { NavigationSplitView(columnVisibility: $columnVisibility) { sidebarList } detail: { detailView } } else { NavigationSplitView(columnVisibility:

You can export a CSV file and have something sort of like this. While that’ll work, if you’re doing anything serious with CSV files I strongly recommend that you check out the TabularData framework. See the code snippet below. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com import Foundation import TabularData let csv = Aloe Vera, skin healer, Cut from middle, once every three days, cut the leave and use the gel inside for your rash Almond, skin healer, cut the young leaves, daily, soak in water overnight rinse and blend func main() throws { var options = CSVReadingOptions() options.hasHeaderRow = false let frame = try DataFrame.init(csvData: Data(csv.utf8), options: options) print(frame) // ┏━━━┳━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━┳… // ┃ ┃ Column 0 ┃ Column 1 ┃ Column 2 ┃… // ┃ ┃ ┃ ┃ ┃… // ┡━━━╇━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━╇… // │ 0 │ Aloe Vera │ skin

The problem is there even in Apple's sample Bringing robust navigation structure to your SwiftUI app | Apple Developer Documentation: on Mac Related Recipes cannot be selected after choosing Experience > Two Columns > Dessert > Apple Pie.

Could you please provide a navigation sequence showing the issue? For example the following works as expected under iOS in portrait mode: Two Columns > Dessert > Apple Pie > Related Recipes: Pie Crust shows the details for Pie Crust

Since List is very versatile, I'm not sure why it cannot be used here. For example, the following works fine in iOS and iPadOS (by persisting the selection): import SwiftUI class Q708440NavigationModel: ObservableObject { @Published var selectedThingId: Thing? } struct Thing: Identifiable, Hashable { let id: UUID = UUID() let name: String } class ThingData: ObservableObject { @Published var things: [Thing] = [ Thing(name: One), Thing(name: Two), Thing(name: Three) ] } struct ThingDetail: View { let thing: Thing @EnvironmentObject var navigationModel: Q708440NavigationModel var body: some View { Text(Thing: (thing.name)) } } struct SomeOtherViewHere: View { var body: some View { Text(Some other view) } } @main struct Q708440App: App { @StateObject var navigationModel = Q708440NavigationModel() @StateObject var thingData = ThingData() var body: some Scene { WindowGroup { Q708440(things: $thingData.things) .environmentObject(navigationModel) } } } struct Q708440: View { @Binding var things: [Thing] @EnvironmentO

For three column layouts, try setting the selected state of the middle column to nil onDisappear as done in ThreeColumnContentView within https://developer.apple.com/documentation/swiftui/bringing_robust_navigation_structure_to_your_swiftui_app

Yes, best to use the new APIs as suggested in https://developer.apple.com/wwdc22/10054 There is a bug (mentioned in my earlier post) with NavigationSplitView with the navigation on a single column, but this is marked as a known issue in iOS 16 beta (3, 4) release notes.

When I followed the procedure to symbolicate an external file by changing the .ips extension to .crash, adding an external device, viewing All Logs and dragging the .crash file from MacOS12.4 Finder to the LH column, a part of the log appear in the RH window but does not include any frame data. The last line is Crashed Thread: 0 Dispatch queue enabled. Right-clicking on the added file and selecting Re-Symbolicate Log results in nothing happening. If I click Done and open View All Logs again, the added file is not present. I presumed this was due to lack of debug symbols but from your comment this is not the case.