-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Known Issues
From Swift 1.2, the compiler no longer allows to override class func load()
method, so you need to manually enable IQKeyboardManager using the below line of code in AppDelegate.
IQKeyboardManager.sharedManager().enable = true
For CoacoaPods or Carthage, IQLayoutGuideConstraints may not be visible in the storyboard. For a workaround, you should set it programmatically
If the keyboard does not appear in iOS Simulator and the only toolbar is appearing over it (if enableAutoToolbar = YES), then check this setting
Xcode 6:- Goto iOS Simulator->Menu->Hardware->Keyboard->Connect Hardware Keyboard, and deselect that.
Xcode 5 and earlier:- Goto iOS Simulator->Menu->Hardware->Simulate Hardware Keyboard, and deselect that.
If you set [[IQKeyboardManager sharedManager] setEnable:NO] and still automatic toolbar appears on textFields? Probably you haven't heard about @property enableAutoToolbar.
@property enable: It enables/disable managing distance between keyboard and textField, and doesn't affect autoToolbar feature.
@property enableAutoToolbar: It enable/disable automatic creation of toolbar, please set enableAutoToolbar to NO if you don't want to add an automatic toolbar.
Now IQKeyboardManager can work with topLayoutConstraint and bottomLayoutConstraint with a bit of manual management. Please check below Manual Management->Working with TopLayoutGuide and BottomLayoutGuide section.
(#374)
This issue happens when there is a textField active on a view controller and you navigate to another view controller without resigning currently active textField. This is an iOS issue and happens even if you don't integrate the library.
For a workaround, you can resign currently active textField in viewWillDisappear
method.
-(void)viewWillDisappear:(BOOL)animated
{
[super viewWillDisappear:animated];
[self.view endEditing:YES];
}
This issue happens in Xcode 9 iOS 11 most probably while using UIPickerView.
For a workaround, you can do the following in your view viewDidLoad
self.pickerView.translatesAutoresizingMaskIntoConstraints = false
This issue happens when the user navigates to another screen while the keyboard is still shown on the current screen.
For a workaround, you can endEditing
the view in your viewWillDisappear
override func viewWillDisappear(_ animated: Bool) {
super.viewWillDisappear(animated)
view.endEditing(true)
}
This issue usually happens when you write becomrFirstResponder
in viewDidLoad or viewWillAppear. Since the library does not know the view position when viewDidLoad or viewWillAppear is getting called, the library behave abnormally.
For a workaround, call becomeFirstResponder
from viewDidAppear