Closed migueldeicaza closed 3 years ago
So this can happen when you have a UIView that is being surfaced to SwiftUI and you "rehost it" into another SwiftUI view that is going to be displayed and are visible at the same time.
To trigger this, I would have the iPad version running, and the menu on the left being shown, with a terminal on the right; And then you tap "Session" on the left, which would rehost the uiview to render it into the sessions display, and that would trigger a crash on the becomeFirstResponder.
There is now a bandaid that essentialy ignores the becomeFirstResponder for now in this very narrow scenario.
Happens when going to Sessions, or returning from Sessions: