[UIKit] Fixes UIGestureRecognizer default introduced in iOS 13.4 #8261
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
Fixes xamarin/Xamarin.Forms#10162 Fixes xamarin#8255 Xcode 11.4 introduced a new protocol member to `UIGestureRecognizerDelegate` and our initial proposed default value for `ShouldReceiveEvent` is not playing well with the world.
dalexsoto
added
the
note-highlight
chamons
approved these changes
Apr 1, 2020
|
In particular see: |
mandel-macaque
approved these changes
Apr 1, 2020
spouliot
approved these changes
Apr 1, 2020
mandel-macaque
approved these changes
Apr 1, 2020
|
@monojenkins backport d16-6 |
|
Build failure Test results1 tests failed, 86 tests passed.Failed tests
|
|
Known failure: HE0038 |
|
@monojenkins backport master |
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.
fixes xamarin/Xamarin.Forms#10162
fixes #8255
Xcode 11.4 introduced a new protocol member to
UIGestureRecognizerDelegateand our initial proposed default value forShouldReceiveEventis not playing well with the world.