On the iPhone, send the applicationContext on the main queue. On the main queue. It worked fine for me in the simulator.

I'm having this issue with Xcode Version 14.0 beta 4 (14A5284g), but I do see that it updates on the Watch Simulator after I quit and restart the Apple Watch app. It doesn't receive applicationContext while the iPhone simulator and watch simulator are up and running together.

The newly added Watch App had some build settings to set. Now it works fine and uses a NavigationStack!

The newly added Watch App had some build settings to set. Now it works fine and uses a NavigationStack!

Fixed by deleting watch target and adding it back in. Now the watch doesn't receive messages, but this issue is resolved.

I created a new project and deleted the WatchApp target. I then added a WatchApp target and copied the files from my existing project over. Now the watch navigates using NavigationStack, but it does not receive messages from the iPhone. There's always something.

I'm using Version 14.0 beta 4 (14A5284g) of Xcode.

I filed a bug report on this. FB10908690 (NavigationStack - No Back Button). I apologize for having another post on this with the same issue. I hope that someone in the know will respond. I know this is not a bug that others have reported. I'm using Version 14.0 beta 4 (14A5284g) of Xcode.

To be complete, it's missing the title and I guess the whole navigation bar.

I don't know what you mean about the 'Numbers' file. To start, you should create a struct to store your plant's data and collectively, form an array of plants. Something like the following struct Plant: Hashable, Identifiable {     let id = UUID() var plantName = ""     var medicinalProperties: [MedProp]? = nil     var harvestInstructions = ""     var waterRequirement = ""     init?(plantName: String = "", medicinalProperties: [MedProp]? = nil, harvestInstructions: String = "", waterRequirement: String = "") { self.plantName = plantName        if let medicinalProperties = medicinalProperties { self.medicinalProperties = medicinalProperties }         self.harvestInstructions = harvestInstructions         self.waterRequirement = waterRequirement     } } struct MedProp: Hashable, Identifiable {     let id = UUID()     ... } There's a lot more to this than just the data models. If you want to learn SwiftUI, I suggest following Apple's excellent SwiftUI Landmarks tutorial. This will help you through the whole process while introducing you to SwiftUI.

I filled a bug report on this. FB10908690 (NavigationStack - No Back Button)

Why do you have VStacks within a VStack? It seems to me that you could ditch (get rid of) the inner VStacks.

I recommend using the init NavigationLink { DestinationView() } label: { LabelView() } The version you are using is deprecated in iOS 16.

It would be clearer if you had embedded your code in a code block.

I'm hoping for some guidance, whether it's a known bug or whether there's something stupid that I am doing. I don't discount the latter, which is why I've been easter-egging my project, but I think it's the former.