I noticed that when this code is run the main viewController sends itself a message to become the firstResponder making it able to receive remote control events. This works as expected, but the viewController loses its firstResponder status when the text field becomes the firstResponder. Because of this, when this app is run and the text field never becomes firstResponder (ie never tapped by user), the remote control events work as expected. As soon as the text field is tapped, the viewController loses firstResponder status and never gets it back.
The fix is rather simple, just call [self becomeFirstResponder] after the text field resigns firstResponder status.
I noticed that when this code is run the main viewController sends itself a message to become the firstResponder making it able to receive remote control events. This works as expected, but the viewController loses its firstResponder status when the text field becomes the firstResponder. Because of this, when this app is run and the text field never becomes firstResponder (ie never tapped by user), the remote control events work as expected. As soon as the text field is tapped, the viewController loses firstResponder status and never gets it back.
The fix is rather simple, just call [self becomeFirstResponder] after the text field resigns firstResponder status.