Issue with UITextField secureTextEntry = YES

[paulyoung]

I hope this is the right forum for this type of question. If not I can post to StackOverflow instead.

I'm using v2.0-RC-2 and have set up a view controller, view model and a view which contains several text fields.

The current setup is similar to an example from the documentation where the submit button is enabled when the view model is valid (currently when all properties have length > 0).

Everything works well except for when I set secureTextEntry = YES on a text field. If that field already has text entered (either pre-populated by the view model, or entered by the user), I'm able to focus on the field and clear the text without the button being disabled.

I believe this is to do with the unique behavior of a text field with secureTextEntry = YES which clears the entire field on the first keypress (not just "delete") after gaining focus.

If I type something and then delete it again, since I'm already focused I must delete each character individually and the button is disabled as expected.

I'm assuming this is something to do with the UITextFieldTextDid... notifications so not sure if a change to RAC can address this, but would appreciate any help in finding a workaround if not.

Thanks.

[paulyoung]

FWIW I tried explicitly setting _passwordField.clearsOnBeginEditing = NO; as a workaround but it had no effect.

[kastiglione]

Are you saying the text field is always being cleared on focus, even with clearsOnBeginEditing set to NO?

If you'd like a signal that captures the event that clears the field, you could create your own signal based on -rac_textSignal's implementation. Instead of using UIControlEventEditingChanged, use UIControlEventAllEditingEvents.

[paulyoung]

Not on focus, but on the first keypress after gaining focus. When this happens I get into a weird state, as if the change didn't register.

I'll give your suggestion a try and report back.

[paulyoung]

I tried this and it seems that no event is fired when the field is cleared in this way.

[paulyoung]

The behavior I'm seeing is described in this StackOverflow question.

[paulyoung]

I believe that this event not being triggered is a bug with the iOS SDK I'm targeting so I filed a Radar.

[kastiglione]

Thanks for the follow up. I'll close this issue.

[paulyoung]

For reference: rdar://14904641

[paulyoung]

This issue was fixed in one of the betas after I filed the radar.