When there is a NavigationLink in a container with an Image (that is resizable, scaled to fill, and clipped to a smaller frame), the NavigationLink cannot be pressed. I'm assuming that this has to do with the parts of the Image that have been "clipped off" still actually present and blocking the NavigationLink.

Here is a short example to replicate the behavior:

```
struct ContentView: View {
    var body: some View {
        NavigationView {
            VStack {
                VStack {
                    NavigationLink(destination: Text("Hello, world!")) {
                        Text("Press me")
                    }
                }

                Image("background")
                    .resizable()
                    .scaledToFill()
                    .frame(height: 60)
                    .clipped()
            }
        }
    }
}

```

"background" can be any sort of picture from the assets folder.

I have tried to mess around with the zIndexes; that didn't work.

There was one hack that worked: I used a UIImage, cropping it to the aspect ratio of Image I wanted by converting it to a CGImage and back into a UIImage. After doing that, I could press on the NavigationLink again but it was obvious from my phone lagging that it was too expensive. I tried to work around this by saving the cropped image to the documents directory and then whenever the aspect ratio wasn't similar enough I would recrop, save, and reload the image, but this still took a toll on the performance of my project.

Please offer some advice on how I should handle this situation. Thanks in advance for any help.