I have tried 4 methods above one by one. Disabling "Connect Hardware Keyboard" seems only to affect the behavior of simulators, but not the canvas. I switch to different simulators, including iPhone & iPad. But the problem is still there. I add a brand new swiftui view and make it to be the simplest codes. But it is still no go. struct TextFieldPopupView: View {     @State private var text = ""     var body: some View {         TextField("Hello", text: $text)             .textFieldStyle(RoundedBorderTextFieldStyle())     } } struct TextFieldPopupView_Previews: PreviewProvider {     static var previews: some View {         TextFieldPopupView()     } } Removing derived data and restarting has no effect yet. Thank you all the same.

It indeed works. However, the problem comes again, if I replace ".frame(maxWidth: geo.size.height*0.6, maxHeight: geo.size.height)" with ".frame(maxWidth: min(geo.size.width * 0.45, geo.size.height * 0.6), maxHeight: geo.size.height)". I'm afraid "Lazy" seems to be the real reason. The grid doesn't load every buttons conditionally. In other words, the buttons in the last row are only loaded sometimes according to the available space probably, I guess. But what's the exact condition? In this case, the space seems to be enough to display all the buttons, but the last row isn't loaded at all. Something must have happened during rotating the simulator.

@OOPer By default, when the picker is tapped, the corresponding option will be selected. In addition to this，I also need to execute some other codes as long as any area within picker is tapped, no matter which option is selected. In other words, I need to know which option user taps, at the mean time I also need to know user is tapping within the picker scope.

@workingdogintokyo That's true. And long pressing on the option will also work. However, I want users can just click on it to select options. Otherwise, it seems to have a little bug, from the users' perspective.

Yes, the issue only happens when I tap the button in edit mode. I will read the linked post, thank you.

xcode14.1, simulator iOS16.1

Thank you for reply! I ran the code on an iPhone 14 simulator. The launch screen image overlapped the notch which indicates the issue will happen on a simulator in runtime. I have no real iPhone 14 device for now. I wonder whether the problem will happen or not on a device.