Just confirming we're seeing this as well.When receiving taps from a UITextField what was `UITapGestureRecognizer` is now `UITextMultiTapRecognizer`, which is undocumented.

I tried this with an iOS 13.4 device:override public func awakeFromNib() { let tapRecognizer = UITapGestureRecognizer(target: self, action: #selector(receivedTap)) addGestureRecognizer(tapRecognizer) } @objc func receivedTap(_ gestureRecognizer: UIGestureRecognizer) { } override public func gestureRecognizerShouldBegin(_ gestureRecognizer: UIGestureRecognizer) -> Bool { NSLog("gestureRecognizerShouldBegin") }If I break in gestureRecognizerShouldBegin in the debugger I first getpo gestureRecognizer <UITextMultiTapRecognizer: 0x144925620 (UITextInteractionNameSingleTap); state = Possible; delaysTouchesEnded = NO; view = <GreyTextField 0x150650000>; target= <(action=onStateUpdate:, target=<UITextMultiTapRecognizer 0x144925620>)>>Followed by the UITapGestureRecognizer we are expecting. This a behaviour change. Prior to 13.4 we would get a UITapGestureRecognizer from built-in gesture recognizers in UITextField, in 13.4 we do not and need to define the gesture directly.

I found a workaround for this issue. We were using NSHealthShareUsageDescription as the key for the localized string in our plist, i.e. In our plist we had "NSHealthShareUsageDescription" => "NSHealthShareUsageDescription" And then in our localized strings we had "NSHealthShareUsageDescription" => "Some localized string" Swapping the key of the localized string over the full EN localized string has fixed the issue. I.e. our plist now has "NSHealthShareUsageDescription" => "Some localized string" And our localized strings has "Some localized string" => "Some localized string" (localized)