You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure how to reproduce, but has been showing up in my crash logs. Here is the section that has problems (line 222):
- (void)inputKeyboardDidShow
{
// Grab the keyboard view
self.keyboardActiveView = self.keyboardActiveInput.inputAccessoryView.superview; // This line causes crashes sometimes
self.keyboardActiveView.hidden = NO;
// If the active keyboard view could not be found (UITextViews...), try againif (!self.keyboardActiveView) {
// Find the first responder on subviews and look re-assign first responder to it
[selfreAssignFirstResponder];
}
}
We're encountering this issue on our app when a keyboard appears after using a UIAlertView with a text view.
It appear that:
The alert view appears and the text field becomes active, setting keyboardActiveInput.
The alert view dismisses causing keyboardActiveInput to become a zombie.
The text view in the original window presents its keyboard without or before posting UITextViewTextDidBeginEditingNotification.
UIKeyboardDidShowNotification is posted, accessing the zombie.
One solution that seems to be working for me is to filter messages to setKeyboardActiveInput: where the responder is not in the same window as the view:
We are seeing this issue as well in our crash reporting system. I was able to isolate one which was a timing issue with presenting an alert at the same time the keyboard was being dismissed. But another instance I am having a hard time tracking down
Not sure how to reproduce, but has been showing up in my crash logs. Here is the section that has problems (line 222):
Here are two of them:
Here is the second one:
I'll update the issue when more information is available.
The text was updated successfully, but these errors were encountered: