-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stealing the firstResponder? #6
Comments
Are you still experiencing this issue? I can't really reproduce it, maybe it's gone since then. |
Actually the bug persists, it happens during the status show / hide animations. not only keys events are eaten but most of the touch events are too. stealing the firstResponder seems to be the right title for this issue :( will test adding UIViewAnimationOptionAllowUserInteraction to the animation options and get back here with the results of my experiements :) |
I'm having this issue too - I couldn't figure things out until I finally contacted Apple support and they suggested I look for places where my key window is being taken over by another window -- MTStatusBarOverlay is a UIWindow class, so I'm guessing if you show a text input in your original key window, launch another window and make it key - UIResponder will now not work for your previous window unless you reset it to key ... does that make sense? I should also note that I have not been able to reproduce this issue -- I just have hundreds of users emailing me about the problem. |
I've been hitting this issue too. I found that whenever I can't type, the status bar overlay window object have become the key window. (lldb) po [[UIApplication sharedApplication] keyWindow] My solution is to add the following code to app delegate. This way whenever the keyboard is shown the main window is forced to be the key window.
However, I'm not sure if this would cause other side effects. |
Just updated to HEAD, now when the statusbar is animating some key events are "eaten" (thus, i'm typing, statusbar changes... keys are missing that really should be there)
The text was updated successfully, but these errors were encountered: