Keyboard management in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

Keyboard Avoidance Behavior

What will happen when the keyboard appears in this SwiftUI view?

iOS Swift

struct ContentView: View {
  @State private var text = ""
  var body: some View {
    VStack {
      TextField("Enter text", text: $text)
        .padding()
      Spacer()
    }
    .padding()
  }
}

A The keyboard will not appear when tapping the TextField.

B The TextField will disappear when the keyboard appears.

C The view will automatically move up so the TextField stays visible above the keyboard.

D The TextField will be covered by the keyboard, making it hard to see what you type.

💡 Hint

Think about default SwiftUI behavior without extra modifiers.

By default, SwiftUI does not automatically move views when the keyboard appears. Without extra code, the keyboard covers the TextField.

❓ lifecycle

intermediate

Keyboard Notification Handling

Which notification should you observe to detect when the keyboard will show in UIKit?

A UIKeyboardWillHideNotification

B UIKeyboardDidHideNotification

C UIKeyboardWillShowNotification

D UIKeyboardDidChangeFrameNotification

💡 Hint

You want to know just before the keyboard appears.

UIKeyboardWillShowNotification is sent just before the keyboard appears, allowing you to adjust UI accordingly.

🔧 Debug

advanced

Fixing Keyboard Overlap Bug

Why does this UIKit code fail to move the view up when the keyboard appears?

iOS Swift

NotificationCenter.default.addObserver(self, selector: #selector(keyboardWillShow), name: UIResponder.keyboardWillShowNotification, object: nil)

@objc func keyboardWillShow(notification: NSNotification) {
  let keyboardSize = (notification.userInfo?[UIResponder.keyboardFrameEndUserInfoKey] as? NSValue)?.cgRectValue
  self.view.frame.origin.y = -keyboardSize!.height
}

A The keyboard size is not unwrapped safely, causing a crash.

B The view's frame is changed but not reset when keyboard hides, causing layout issues.

C The notification name is incorrect and never triggers the method.

D The selector method is not marked @objc, so it won't be called.

💡 Hint

Think about what happens when the keyboard disappears.

The code moves the view up but does not move it back down when the keyboard hides, so the view stays shifted.

❓ navigation

advanced

Keyboard and Navigation Controller Interaction

In a UINavigationController stack, what is the best way to ensure the keyboard does not cover input fields on pushed view controllers?

A Adjust the scroll view's contentInset and scrollIndicatorInsets when keyboard shows and hides.

B Manually move the entire navigation controller's view up by keyboard height.

C Disable the keyboard to prevent it from appearing.

D Set the navigation bar to hidden when keyboard appears.

💡 Hint

Think about scroll views and their built-in support for content adjustment.

Adjusting contentInset and scrollIndicatorInsets of scroll views is the standard way to keep inputs visible when keyboard appears.

🧠 Conceptual

expert

SwiftUI Keyboard Management Best Practice

Which approach is recommended to handle keyboard avoidance in SwiftUI for complex forms?

A Use GeometryReader and keyboard height notifications to adjust view padding dynamically.

B Wrap the entire view in a ScrollView and rely on default behavior without adjustments.

C Disable the keyboard and use custom input views instead.

D Use UIKit UIViewControllerRepresentable to manage keyboard and ignore SwiftUI layout.

💡 Hint

Think about combining SwiftUI layout tools with keyboard info.

Using GeometryReader with keyboard height notifications allows dynamic padding adjustments to keep inputs visible in SwiftUI.

Practice

1. What is the main purpose of managing the keyboard in an iOS app?

easy

A. To disable typing in text fields

B. To keep input fields visible when the keyboard appears

C. To change the keyboard color

D. To automatically save user input

Solution

1. Step 1: Understand keyboard impact on UI

   The keyboard can cover input fields, making them hard to see or use.

2. Step 2: Purpose of keyboard management

   Managing the keyboard ensures input fields stay visible and accessible when typing.

3. Final Answer:

   To keep input fields visible when the keyboard appears -> Option B

4. Quick Check:

   Keyboard management = keep inputs visible [OK]

Hint: Keyboard management keeps inputs visible when typing [OK]

Common Mistakes:

• Thinking keyboard management changes keyboard color
• Believing it disables typing
• Assuming it auto-saves input

2. Which Swift method is used to dismiss the keyboard when tapping outside a UITextField?

easy

A. textField.resignFirstResponder()

B. textField.becomeFirstResponder()

C. textField.showKeyboard()

D. textField.hideKeyboard()

Solution

1. Step 1: Identify method to dismiss keyboard

   Calling resignFirstResponder() on a UITextField tells it to stop being active, hiding the keyboard.

2. Step 2: Check other options

   becomeFirstResponder() shows keyboard; showKeyboard() and hideKeyboard() do not exist in UIKit.

3. Final Answer:

   textField.resignFirstResponder() -> Option A

4. Quick Check:

   Dismiss keyboard = resignFirstResponder() [OK]

Hint: Use resignFirstResponder() to hide keyboard [OK]

Common Mistakes:

• Using becomeFirstResponder() which shows keyboard
• Trying non-existent methods like hideKeyboard()
• Not calling any method to dismiss keyboard

3. Given this Swift code snippet, what happens when the keyboard appears?

NotificationCenter.default.addObserver(self, selector: #selector(keyboardWillShow), name: UIResponder.keyboardWillShowNotification, object: nil)

@objc func keyboardWillShow(notification: NSNotification) {
  if let keyboardSize = (notification.userInfo?[UIResponder.keyboardFrameEndUserInfoKey] as? NSValue)?.cgRectValue {
    scrollView.contentInset.bottom = keyboardSize.height
  }
}

medium

A. Nothing happens when keyboard appears

B. The keyboard is hidden automatically

C. The scroll view scrolls to top

D. The scroll view's bottom inset increases to avoid keyboard overlap

Solution

1. Step 1: Understand notification observer

   The code listens for keyboard showing and calls keyboardWillShow function.

2. Step 2: Adjust scroll view inset

   Inside keyboardWillShow, it sets scrollView.contentInset.bottom to keyboard height, pushing content up.

3. Final Answer:

   The scroll view's bottom inset increases to avoid keyboard overlap -> Option D

4. Quick Check:

   Keyboard show adjusts scroll inset [OK]

Hint: Keyboard show notification adjusts scroll inset bottom [OK]

Common Mistakes:

• Thinking keyboard hides automatically
• Assuming scroll view scrolls to top
• Ignoring contentInset adjustment

4. What is wrong with this Swift code for dismissing the keyboard?

override func touchesBegan(_ touches: Set<UITouch>, with event: UIEvent?) {
  view.endEditing(true)
}

medium

A. endEditing(true) does not dismiss keyboard

B. TouchesBegan is not called on UIViewController

C. It should call super.touchesBegan to propagate touch events

D. The method signature is incorrect

Solution

1. Step 1: Check method override

   Overriding touchesBegan requires calling super.touchesBegan to allow normal touch handling.

2. Step 2: Identify missing call

   The code misses super.touchesBegan, which can cause touch events to stop propagating.

3. Final Answer:

   It should call super.touchesBegan to propagate touch events -> Option C

4. Quick Check:

   Override touchesBegan must call super [OK]

Hint: Always call super in overridden touchesBegan [OK]

Common Mistakes:

• Not calling super.touchesBegan
• Thinking endEditing(true) doesn't dismiss keyboard
• Using wrong method signature

5. You want to move the view up when the keyboard appears and move it back down when it hides. Which approach correctly handles this in Swift?

hard

A. Listen to keyboardWillShow and keyboardWillHide notifications, adjust view frame accordingly

B. Only listen to keyboardDidShow notification and adjust view frame

C. Use a timer to check keyboard height every second and move view

D. Change the keyboard type to avoid covering the view

Solution

1. Step 1: Understand keyboard notifications

   keyboardWillShow and keyboardWillHide notify before keyboard appears/disappears, allowing smooth UI changes.

2. Step 2: Adjust view frame on both notifications

   Adjusting view frame up on show and back down on hide keeps UI consistent and responsive.

3. Step 3: Evaluate other options

   Listening only to keyboardDidShow is late; timer wastes resources; changing keyboard type doesn't solve overlap.

4. Final Answer:

   Listen to keyboardWillShow and keyboardWillHide notifications, adjust view frame accordingly -> Option A

5. Quick Check:

   Use willShow and willHide notifications for UI moves [OK]

Hint: Use willShow and willHide notifications to move views [OK]

Common Mistakes:

• Using only keyboardDidShow notification
• Polling keyboard height with timer
• Trying to change keyboard type to fix layout