The accentColor(_:) modifier is marked as being deprecated with a message saying this: Use the asset catalog’s accent color or tint(_:) instead. Using either of these methods will result in a sheet using this accent colour. If you still want to use accentColor(_:), just reapply this modifier to the sheet content, as a workaround.

Missing argument for parameter 'images' in call The problem you have is the ImageCard view has an images parameter that you haven't specified in the NavigationLink label. Consecutive statements on a line must be separated by ';' You also have a closing parenthesis after the NavigationLink which has no matching opening parenthesis; this triggers a syntax error. Replace the contents of your ForEach with this: NavigationLink { LandCard() } label: { ImageCard(images: images) }

Sorry if I didn't make this clear, but your code from before should look like this: ForEach(ImagesList, id: \.id) { images in NavigationLink { LandCard() } label: { ImageCard(images: images) } } Currently you are showing the ImageCard view twice, the second as a NavigationLink, but I assume that you only need it once. On your second problem, the height of the ImageCard depends on how you create it. Can you show the code for the ImageCard view so that we can understand what is causing the issue?

Thank you for sharing all the code. The probable cause of your height issue is that you have wrapped the contents of your ImageCard body in a NavigationView. You don't need to do this as you are already embedding it in one in ContentView. Remove the NavigationView from ImageCard to see if this helps. If it doesn't help, which I'm sure it will, then it would be down to the fact that you are setting an explicit height of 200 to the ZStack in ImageCard. I'm not sure how much this affects things but changing this value to a smaller one might make a difference.

I would file feedback for this as I can't find a solution, yet.

Controls, like menus and pickers with the menu style, don't work when placed in a view of an NSMenuItem. I believe only simple controls and ones with button-like behaviour do. If you need the menu as it is, and because it would be classed as a complex view, I would recommend using a popover instead. Something like this should work: var statusItem: NSStatusItem? var popover: NSPopover? func applicationDidFinishLaunching(_ aNotification: Notification) {     statusItem = NSStatusBar.system.statusItem(withLength: NSStatusItem.variableLength)     statusItem?.button?.image = NSImage(systemSymbolName: "gearshape.circle", accessibilityDescription: "Logo")     statusItem?.button?.action = #selector(showPopover)     let hostingViewController = NSHostingController(rootView: MenuExtraView())     popover = NSPopover()     popover?.contentViewController = hostingViewController     popover?.contentSize = .init(width: 350, height: 400)     popover?.behavior = .transient } @objc func showPopover(_ button: NSButton) {     popover?.show(relativeTo: button.bounds, of: button, preferredEdge: .minY) } If you just need a standard menu for your status item instead of a view, then add an item like this: menu.addItem(withTitle: "Quit", action: #selector(NSApp.terminate), keyEquivalent: "q")

From the iOS & iPadOS 16 Beta 3 Release Notes: Conditional views in columns of NavigationSplitView fail to update on some state changes. (91311311) Workaround: Wrap the contents of the column in a ZStack. It mentions NavigationSplitView, but it must apply to NavigationStack as wrapping the if statement in your example in a ZStack updates the view.

I forgot to add this, but when you do start to target macOS Ventura, menus and pickers will work properly in a MenuBarExtra with the .window style.

File feedback as this seems to be an issue.

You can assign a value directly to the variable, like this: url = tempUrl

Doing this, like you did in the List example, works fine: ForEach($results) { $result in Image(uiImage: result.image) } Because you are passing a Binding of a collection to the data parameter of the ForEach, the content closure expects to be passed a Binding of one of the collection’s elements. This is why you can access this value with the $ prefix and then read the underlying value, in your case ImageData, without it.

Because you are using a UIKit API in SwiftUI in an “unnatural“ way, I won’t work as expected. You’re right about it being sort of a one-time thing. Even Apple recommends staying away from this method: In general, you should not rely on implementation details of a framework (including SwiftUI) to achieve specific behaviors in your apps. In iOS 16, SwiftUI does gain a new modifier: toolbarBackground(_:for:). You can use it like this: ... .toolbarBackground(.red, for: .tabBar) I believe it only applies to the current view, so you can change the behavior at different levels of the hierarchy. See the documentation as there is a lot more you can customise now regarding bars.

Can you show us some code that will help to explain why this is happening? It seems like you have multiple NavigationViews each with NavigationLinks that cause this stacked appearance.

It might be a bug in watchOS 9. If it’s not, then you can manually control the indicators by adding this parameter to the tab view style: .tabViewStyle(.page(indexDisplayMode: .always))

Setting the values in the AccentColor colour set in the asset catalog to your desired tint colour should work. I don’t know if using the tint(_:) modifier works but you could try that too.