In practice, you’ll probably be dismissing the keyboard from a view controller most of the time anyway, but the nil-targeted action approach (using UIApplication) works from anywhere. The key here is that you need to have a reference to the view, so you can only use this approach from a view controller. One benefit to this approach is that you can use the return value of endEditing to find out whether the keyboard was dismissed or not. Most of the time, you should be able to do the following: Approach #2: Using UIView’s endEditingĪ reader pointed out that you can also use - to dismiss the keyboard (assuming your text field is a subview of the view you call this on). It’s by far the best way to do it: no worrying about who the first responder is. No matter what, this will dismiss the keyboard. This will resign the first responder (and dismiss the keyboard) every time, without you needing to send resignFirstResponder to the proper view. In Objective-C: to:nil from:nil forEvent:nil] In Swift: UIApplication.sharedApplication().sendAction('resignFirstResponder', to:nil, from:nil, forEvent:nil) If you want to dismiss the iOS keyboard programmatically in your app without worrying about which view is the first responder, try the following: Approach #1: Using the Responder Chain

Swift keyboard ipad