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
To reproduce, implement tokenFieldDidBeginEditing: and remove the call to [self.tokenField becomeFirstResponder]; in the sample project's ViewController.m. Launch the app, tap the token field, and notice that tokenFieldDidBeginEditing: is never called.
The text was updated successfully, but these errors were encountered:
No worries! I added a not-quite-perfect fix (the begin/end editing methods get called multiple times) in this fork. Not sure if that will help, but the editing property in VENTokenField would be where to look.
Thanks for the link to the fork! Yeah I’ve been struggling to find an elegant way to fix this. I’ve gone down some rabbit holes of UITextFieldDelegate method hell. I think it might be the case that we need some sort of state to keep track of whether or not that delegate method should be called (I’m guessing that’s what the editing property is essentially tracking?).
To reproduce, implement
tokenFieldDidBeginEditing:
and remove the call to[self.tokenField becomeFirstResponder];
in the sample project's ViewController.m. Launch the app, tap the token field, and notice thattokenFieldDidBeginEditing:
is never called.The text was updated successfully, but these errors were encountered: