[iOS 17] Fix navigation to safari not working when keyboard is visible #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iOS 17 adds SwiftUI.UIKitKeyPressResponder to responder chain between inserted UIView and first UIViewController which is neither an UIView or UIViewController. This causes the search for UIViewController to fail.
stleamist
approved these changes
Oct 29, 2023
stleamist
changed the base branch from
main
to
bug/ios-17-key-press-responder-issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
iOS 17 adds SwiftUI.UIKitKeyPressResponder to responder chain between inserted UIView and first UIViewController which is neither an UIView or UIViewController. This caused the search for UIViewController to fail before fix.