A Picker with the .menu picker style won't use the view specified in the label closure. It will generate its label based off of the currently selected item. This is the default behaviour. If you want a custom label, use a standard Menu and add your Picker inside of that. Note, you won't get the iOS 16 style double chevron indicator.

It seems the problem lies with the if-else statement and the way SwiftUI handles view identity and layout. First of all, you need to be animating changes to the rooms property otherwise there will be no animated transition. Something like this can work, but there are other ways: withAnimation { rooms.append(newRoom) } As the List will not be shown when it has no items, you can use a single if statement for the loading text, and the transition which will work as expected. Here's how it would look: ZStack { if items.isEmpty { Text("Loading...") .transition(.slide) .zIndex(1) // place above the List (with ZStack) } List(selection: $selectedRoom) {     ...               } }

You need to move the sheet modifier outside of the ForEach, as it's currently creating a sheet for every item bound to the same isPresented variable. When you set isPresented to true, you are essentially showing each item's sheet, but you only see the last one. You can instead use the sheet(item:onDismiss:content:) modifier. Something like this will work: // the item parameter requires the data to be Identifiable // you can make a custom struct to hold this, or manually conform String to Identifiable struct Item: Identifiable { let id = UUID() let name: String } // you can remove the isPresented variable @State selectedItem: Item? var body: some View { ... ForEach(...) { item in Button { selectedItem = Item(name: item) } label: { ... } } // move outside loop so there is only one sheet that shows a view dependant on the selectedItem .sheet(item: $selectedItem) { item in CustomView(text: item) } ... }

Because you're using a List with selection enabled, the whole row will be selected/highlighted – that's the default behaviour. What do you mean by only the title text be selectable? Do you only want the title text to respond to taps, or do you only want the title text to be highlighted when selected?

Update I have just created a new macOS project with Core Data enabled and run the program without modifying the template code. Even though the onDelete(perform:) modifier has been attached to the ForEach, the delete swipe action won't work as the List is in a sidebar-style state. If you change the list style to something different, like .inset, the swipe action will work. You could use the onDeleteCommand(perform:) modifier where you can delete the currently selected item in the List when the delete key is pressed. You could also add a contextMenu(menuItems:) modifier and add your own Button that deletes the selected item.

The onDelete(perform:) modifier should cause list rows to be deleted through a swipe action. Are you saying this isn't working?

is there any way to deal with this optional? What error are you getting exactly? Is it a simple "Unexpectedly found nil while unwrapping an Optional value" sort of thing? You will need to check that the value in the url property is a genuine URL. You could provide a default URL, maybe this: URL(fileURLWithPath: "/dev/null") but it's up to you and how you manage that url property. ‎ ‎ I must associate destination to Recording.url In the importing closure you would need to return an instance of Recording, given the file URL (received.file). What the example it doing is copying the received file to a location in the user's file system and using that new URL to create a Video object. If you look at the Copy Code snippets for that session, you can see the contents of the Video.copyVideoFile method. So yes, the received/copied destination file URL needs to be assigned to the Recording.url property. ‎ ‎If there are additional issues, please create a new post as this one is about a different (solved?) problem. Don't forget to close this thread.

You are using the ShareLink initialiser that accepts a String or URL as the item parameter. You instead need to use an initialiser with the preview parameter which accepts a Transferable object and requires a SharePreview.

Where are you calling changeShow()? The code you provided should work fine. Can you show some more code which would reveal the problem. I tested with this code and tapping the "Text" showed and hid the "Bar" text. var body: some View { Text("Text") .onTapGesture { isText.changeShow() } if isText.show {        Text("Bar")     } }

Thanks for clearing things up. I have found that the previously mentioned modifier should be applied to each view inside of the TabView for it to take effect, like this: TabView { Tab1() .toolbar(.hidden, for: .tabBar) Tab2() .toolbar(.hidden, for: .tabBar) Tab3() .toolbar(.hidden, for: .tabBar) ... } Hopefully that should work. However, I believe there is still the problem of the "More" tab that arises from the TabView's five tab limit. When selecting one of these tabs from the custom tab bar, the view is shown, unexpectedly to the user, in the "More" navigation stack, which isn't pleasant to use. I don't think there is a way to remove this feature, so there are probably only two solutions to this: Only have a maximum of five tabs, or Use the custom tab bar approach without the TabView.

I don't understand what the problem is here. You have a native SwiftUI TabView that has its own tab bar (which I think you want to hide), and then a custom tab bar that overlays the system one. It seems like the more tab, that appears when there are more than five tab items, is affecting you're custom tab bar approach. Is this correct? Also, why do you have a system tab bar if you're not going to use it? Just use an if or switch statement, without the TabView, to change between the tabbed views based on what the user has selected from the custom tab bar.

If you want to hide the tab bar, you can use the new modifier introduced in iOS 16: toolbar(_:for:). You would use it like this: .toolbar(.hidden, for: .tabBar)

Maybe this will explain things (from the macOS and Xcode release notes): ‎ The macOS 13 SDK provides support to develop apps for Mac computers running macOS 13 Ventura beta 7. The SDK comes bundled with Xcode 14 beta 6 ... Xcode 14 RC includes Swift 5.7 and SDKs for iOS 16, iPadOS 16, tvOS 16, watchOS 9, and macOS Monterey 12.5.

It happens when you develop for iOS, iPadOS, and MacOS. Make sure that your macOS minimum deployment target is set to version 13.0, otherwise NavigationStack will not be available. I'm assuming you're iOS target version is 16.0. ‎ Just installed Ventura beta 7, now two new additional errors.. Double-check you are targeting iOS 16 and/or macOS 13 where NavigationStack, and other new APIs, are available. If not, you will have to provide more information on where these errors are coming from.

Strange. I am not having this problem on Xcode 14 RC. Are you sure you have imported SwiftUI?