resignFirstResponder not hiding keyboard on textFieldShouldReturn

Question

I have a view with a UITextField which should hide the keyboard when return is pressed.

My function is this:

- (BOOL)textFieldShouldReturn:(UITextField *)textField {
 if ( textField == userPassword ) {
  [textField resignFirstResponder];
 }
 return YES;
}

Normally the keyboard should be hidden but it stays on the screen. resignFirstResponder is correctly called. What am I missing?

Have you tried returning NO? Returning YES may cause the text field to run some code which would make it first responder again. — rickharrison, Jun 26 '10 at 22:38
Yes I did, it changed nothing. The focus however seems to be removed from the field, the (X) on the right side to clear the fields content is no longer shown after resignFirstResponder — favo, Jun 27 '10 at 07:22

score 49 · Accepted Answer · edited May 23 '17 at 12:00

49

I see you have the iPad tag on this. Do you happen to be presenting a modal view using UIModalPresentationFormSheet? If so, it looks like this is a limitation of the FormSheet modal presentation (either Apple is doing it intentionally for some reason, or it is a bug). See these other questions for more details:

Modal Dialog Does Not Dismiss Keyboard

Modal View Controller with keyboard on landscape iPad changes location when dismissed

edited May 23 '17 at 12:00

Community

1
1

answered Feb 21 '11 at 19:54

Brandon

953
10
12

thats exactly what is happening, thank you, I accepted your answer because it explains that this is some Apple behaviour/bug – favo Feb 27 '11 at 15:10
1

Wow, it took me a while to find this answer and it works perfectly. I had no ide it was related to a UIModalPresentationFormSheet. – zachzurn May 03 '12 at 07:03
5

tony.stack's answer actually fixes the issue. – Daniel T. Aug 16 '12 at 15:37
1

I solved this by executing `resignFirstResponder` in the main queue.. Hope this helps anyone – Matej Nov 29 '14 at 12:55

score 33 · Answer 2 · edited Dec 02 '14 at 09:39

33

There is this helpful method which allows you to dismiss the keyboard when presenting the Modal Dialog:

 - (BOOL)disablesAutomaticKeyboardDismissal { return NO; }

This will override the default behavior of the modal dialog set by Apple and allow you dismiss the keyboard. It is in the UIViewController Class.

I hope this helps someone!

edited Dec 02 '14 at 09:39

jomo

14,121
4
29
30

answered May 02 '12 at 21:14

tony.stack

780
8
21

1

The behavior is intentional on Apples part. Read the docs for disablesAutomaticKeyboardDismissal. Thanks Tony, this helped a lot! – Daniel T. Aug 16 '12 at 15:36
1

This solution is good. If you are looking for a fix, try it. Worked for me. – Sparklellama Nov 20 '12 at 22:43
1

Put it in the class that invokes the UITextView or Text Thingy for your Keyboard. – tony.stack Dec 21 '12 at 16:57
1

Use lower case r in return ;) – Michael Morrison Sep 01 '13 at 03:16
changed to lower case r in return! ty! – tony.stack Sep 05 '13 at 15:48
2

this is THE answer! The long awaited mystery solved. – Laszlo Dec 16 '13 at 17:05
4

I had to subclass UINavigationController and add this method in there. This was because my Modal view controller Root was a NavigationController. – theiOSDude Dec 23 '13 at 10:39
1

To be put in the class that is presented as a modal. – Jon - LBAB Jul 29 '14 at 14:28

score 10 · Answer 3 · answered Aug 13 '10 at 17:23

10

If you are using the Interface Builder, look if your UITextField has the delegated linked with your class.

-Select your UITextField and in your Connections look if exits one connection in Outlets->delegate. If not, conect with you File's Owner Class.

This need to be linked with your File's Owner Class. This delegate tell where to search for a method. If your are overriding a method, you need to tell where the object will search for that.

answered Aug 13 '10 at 17:23

Marcos Issler

115
1
9

The responder is correctly called, its not a matter of the delegate. Thank you for trying :-) – favo Aug 14 '10 at 16:21

score 7 · Answer 4 · answered Sep 27 '12 at 21:44

This solution worked for me after none of the above did. after calling resignFirstResponder i added a modal view & removed it.



    [myTextField resignFirstResponder];
    UIViewController *dummyController = [[UIViewController alloc] init];
    UIView *dummy = [[UIView alloc] initWithFrame:CGRectMake(-1, -1,1,1)];
    [dummyController setView:dummy];
    [self presentModalViewController:dummyController animated:NO];
    [dummyController dismissModalViewControllerAnimated:NO];

Keyboard animation is gone (as are my animations associated with it) but yeah, this is the only solution that works for me. — Kalle, Dec 04 '14 at 06:01

score 4 · Answer 5 · answered Nov 18 '11 at 19:31

To deal with the bug mentioned by Brandon, you can try closing and re-opening your modal view controller as long as you still have a reference to it.

[textField resignFirstResponder];
[self dismissModalViewControllerAnimated:NO];
[self presentModalViewController:yourModalViewControllerReference animated:NO];

(where "self" should be the controller you used to originally open the modal view controller)

score 3 · Answer 6 · edited Dec 12 '12 at 07:09

3

xcode 4.5.1

Simply click control then on the textfield drag and release on the .h file

(control key+ drag)

then in the pop up menu select

connection=acton;
name= any name;
type=id;
event=did end on exit;
arguments=sender;

then click connect button

edited Dec 12 '12 at 07:09

Sven Hohenstein

80,497
17
145
168

answered Dec 12 '12 at 06:49

madusanka

41
2

score 3 · Answer 7 · answered Jan 18 '11 at 02:35

3

I was having the same problem. I realized that after connecting the delegate to the File's Owner in Interface Builder, I neglected to save in Interface Builder. Once I saved, I recompiled and the keyboard disappears correctly when hitting return.

answered Jan 18 '11 at 02:35

jmundie

31
1

score 2 · Answer 8 · answered Jan 31 '11 at 01:51

2

Did you remember to implement the UITextFieldDelegate protocol?

answered Jan 31 '11 at 01:51

WrightsCS

50,551
22
134
186

1

If you implement the UITextFieldDelegate protocol you can inadvertently cause this behavior if you do text validation. If your validation codes returns false from textFieldShouldEndEditing when the text is invalid, the field can't relinquish it's firstResponder status and the keyboard will remain on screen in the next view. More details at http://stackoverflow.com/questions/8379205/uitextfields-keyboard-wont-dismiss-no-really/37082876#37082876 – SafeFastExpressive May 06 '16 at 23:44

score 1 · Answer 9 · edited May 25 '14 at 17:48

I have read so many articles about this issue, where the onscreen keyboard refuses to hide when you call resignFirstResponder, but none of the suggestions worked for me.

I'm using XCode 5 (iOS 7) and have a iPhone screen containing a couple of controls which require the onscreen keyboard, but if the user clicks on the UIButton, then I want the keyboard to disappear.

enter image description here

I probably wasted one full day experimenting with resignFirstResponder and adding disablesAutomaticKeyboardDismissal functions to return NO, but nothing worked. Once the onscreen keyboard appeared, I could never get it to disappear again.

But then I had a small brainwave (as I only have a small brain).

Now, when the user clicks on my UIButton, I simply disable the UITextField and UITextView controls.

- (IBAction)btnDate_Tapped:(id)sender {
    //  The user has clicked on the "Date" button.
    self.tbClientName.enabled = NO;
    self.tbComments.editable = NO;

And suddenly, the app finds it has no editable text fields needing an onscreen keyboard, and it neatly slides the keyboard out of sight.

(Relieved sigh.)

My UIButton actually makes a popup dialog appear. When the user dismisses the popup, I re-enable these two controls, so if the user taps in one of them, the keyboard will appear again.

-(void)popoverControllerDidDismissPopover:(UIPopoverController *) popoverController {
    //  The user has closed our popup dialog.
    //  We need to make our UITextField and UITextView editable again.
    self.tbClientName.enabled = YES;
    self.tbComments.editable = YES;
    ... etc...
}

Simple, isn't it !

And surprisingly, this workaround even works on UIViewControllers which appear in Modal style.

I hope this helps other XCode victims out there.

Please help Ive also been struggling with this for a full day now! I have done everything you've said is there anything else that could possible differ in your app that i can change in mine? — 4GetFullOf, Apr 22 '14 at 22:10
My UIButton is shown in the screenshot above (showing the date/time). When the user clicks on this, I wanted the onscren keyboard to disappear, and a popup to appear, where they could select a date. — Mike Gledhill, May 09 '14 at 08:46

score 0 · Answer 10 · edited Oct 20 '12 at 15:30

0

The easiest way is:

Go to your user interface builder,
select UITextField and "Control-Drag" to "Detail View Controller-Detail" and release.
The window will pop-up. Then under "Outlets" select "Delegate".

That's it. It worked for me.

edited Oct 20 '12 at 15:30

atxe

5,029
2
36
50

answered May 24 '12 at 20:14

Timur Nurullaev

1

score 0 · Answer 11 · edited Jun 09 '14 at 14:52

0

if you are in UIModalPresentationFormSheet just call

- (BOOL)disablesAutomaticKeyboardDismissal
{
    return NO;
}

edited Jun 09 '14 at 14:52

Parth Bhatt

19,381
28
133
216

answered Feb 06 '13 at 08:52

Jeremy Piednoel

407
2
5
12

1

I have already given that answer almost a year earlier - FYI. :) – tony.stack Aug 04 '14 at 13:51

Josh O'Connor · Answer 12 · 2016-12-20T01:32:17.590

0

Swift 3.0:

override var disablesAutomaticKeyboardDismissal: Bool {
    get{
        return false
    }
    set {
        self.disablesAutomaticKeyboardDismissal = false
    }
}

edited Dec 20 '16 at 01:32

answered Dec 20 '16 at 01:25

Josh O'Connor

4,694
7
54
98

score 0 · Answer 13 · answered Sep 28 '17 at 05:13

0

Swift 3.0

func textFieldShouldBeginEditing(_ textField: UITextField) -> Bool {

    if textField == addressTextField {
        textField.resignFirstResponder()

        return false
    }

    return true
}

answered Sep 28 '17 at 05:13

krish

3,856
2
24
28

score 0 · Answer 14 · answered Jan 31 '11 at 01:44

Based on your comment that it looks like focus has shifted, then I think what may be happening is that the keyboard is staying open for the next text input field. If your return key is a "Next" key, then returning YES for textFieldShouldReturn: will make the next textField the first responder, and keep the keyboard visible.

resignFirstResponder not hiding keyboard on textFieldShouldReturn

14 Answers14

Linked