IHKeyboardAvoiding is an elegant solution for keeping any UIView visible when the keyboard is being shown - no UIScrollView required!

If you are setting one of the two TextFields to "Secure Text Entry" in the Interface Builder as it is supposed for a password field, the scrolling does not work correctly any more. Didn't this bug also occur in your demo that shows the gif animation? Do you have a workaround?

Hey there, I've updated my pods this morning and I've noticed a regression in the recent commit for version 1.2: the avoiding view is moved down even if the keyboard is not covering it.

If you activate the keyboard while on a phone call, then disconnect the call and dismiss the keyboard, it pushes the view down further than it should go, leaving a black space at the top.

I have the following screen, blue background being the container view and my avoiding view.

However, when I present my keyboard, the container view overlaps with my status bar. Was wondering if there's any way to dodge this? My self.view.clipsToBounds is already set to true if that matters

Hi,

I've updated the version of IHKeyboardAvoiding to the latest Swift version. When executing the following code: KeyboardAvoiding.avoidingView = self

And executing this in an AwakeFromNib which isn't showing itself yet (it's a popup which will show when pressing a button) it will crash saying the following: fatal error: unexpectedly found nil while unwrapping an Optional value

UIView that you previously created for origin calculation does not belong to any UIWindow, so this will give incorrect frame for triggerView in UIWindow coordinates.

Upon open the app in iOS 11.2, the keyboard avoiding is working. But only worked for once then the keyboard avoiding not working anymore. I checked with 11.1.1 , 11.1.2 , 11.2. It seems only happen at 11.2 devices. ( FYI , the issue happens when I using navigation controller and perform segue or unwind segue, after I perform one of those segues , the keyboard avoiding is not working )

It seems like IHKeyboardAvoiding doesn't support auto layout, it only moves KeyboardAvoiding.avoidingView up and down, which could potentially overlaps other views. Here's what in my storyboard

each text field has same distance from its top's, the first one is in the centre of screen. If I click text field 3, it becomes like this

Is there any way that I could achieve this?

The keyboard frame is also dependent on the rotation of the device in iOS 8. So this is causing the avoided view to be moved incorrectly for iOS 8 devices.

I created my own category on UIScreen for returning the correct height or width depending on the iOS version. Maybe you could use something similar for the keyboard frame....

+ (CGFloat)screenWidth
{
    CGFloat width = [self screenSize].width;

    if (![self isiOSEight])
        if ([self isLandscape])
            width = [UIScreen mainScreen].bounds.size.height;

    return width;
}

+ (CGFloat)screenHeight
{
    CGFloat height = [self screenSize].height;

    if (![self isiOSEight])
        if ([self isLandscape])
            height = [UIScreen mainScreen].bounds.size.width;

    return height;
}

#pragma mark - Helpers

+ (BOOL)isiOSEight
{
    return ([[UIDevice currentDevice].systemVersion floatValue] < 8.0) ? NO : YES;
}

+ (CGSize)screenSize
{
    return [UIScreen mainScreen].bounds.size;
}

+ (BOOL)isLandscape
{
    return UIInterfaceOrientationIsLandscape([[UIApplication sharedApplication] statusBarOrientation]);
}

Version: 4.2 Issue: The avoiding view did not update the position if the quick type search bar is dismissed. (P/S : I was implement password autofill for iOS 11 on my apps)

I added IHKeyboardAvoiding.xcodeproj by $swift package generate-xcodeproj and enabled carthage build. You can test the carthage build in two ways.

• $ carthage build --no-skip-current --platform ios.
• $ carthage update --platform ios using below Cartfile.

github "culumn/IHKeyboardAvoiding" "feature/carthage"

Hi I am trying to use in Xcode 12.5 using SPM. I get following error. Can you please guide how i can fix this.

Showing All Messages the manifest is missing a Swift tools version specification; consider prepending to the manifest '// swift-tools-version:5.4.0' to specify the current Swift toolchain version as the lowest Swift version supported by the project; if such a specification already exists, consider moving it to the top of the manifest, or prepending it with '//' to help Swift Package Manager find it in https://github.com/IdleHandsApps/IHKeyboardAvoiding

I have got a crash report from Fabric in the library IHKeyboardAvoiding version 2.6.0. The stack trace below:

Fatal Exception: NSRangeException

0  CoreFoundation                 0x1b329898c __exceptionPreprocess
1  libobjc.A.dylib                0x1b2fc10a4 objc_exception_throw
2  CoreFoundation                 0x1b32ee3f8 -[__NSCFString characterAtIndex:].cold.1
3  CoreFoundation                 0x1b3182c6c -[__NSArrayM objectAtIndexedSubscript:]
4  IHKeyboardAvoiding             0x1054f1730 +[IHKeyboardAvoiding applicationDidEnterBackground:] + 339 (IHKeyboardAvoiding.m:339)
5  CoreFoundation                 0x1b31f409c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__
6  CoreFoundation                 0x1b31f40e4 ___CFXRegistrationPost1_block_invoke
7  CoreFoundation                 0x1b31f3444 _CFXRegistrationPost1
8  CoreFoundation                 0x1b31f30fc ___CFXNotificationPost_block_invoke
9  CoreFoundation                 0x1b316f43c -[_CFXNotificationRegistrar find:object:observer:enumerator:]
10 CoreFoundation                 0x1b31f2a4c _CFXNotificationPost
11 Foundation                     0x1b354f2d8 -[NSNotificationCenter postNotificationName:object:userInfo:]
12 UIKitCore                      0x1b72abd50 __47-[UIApplication _applicationDidEnterBackground]_block_invoke
13 UIKitCore                      0x1b6ca6da0 +[UIViewController _performWithoutDeferringTransitionsAllowingAnimation:actions:]
14 UIKitCore                      0x1b72abb0c -[UIApplication _applicationDidEnterBackground]
15 UIKitCore                      0x1b6a8171c __101-[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:]_block_invoke_2
16 UIKitCore                      0x1b6f113ec _UIScenePerformActionsWithLifecycleActionMask
17 UIKitCore                      0x1b6a812f8 __101-[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:]_block_invoke
18 UIKitCore                      0x1b6a80d50 -[_UISceneLifecycleMultiplexer _performBlock:withApplicationOfDeactivationReasons:fromReasons:]
19 UIKitCore                      0x1b6a81124 -[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:]
20 UIKitCore                      0x1b6a809e0 -[_UISceneLifecycleMultiplexer uiScene:transitionedFromState:withTransitionContext:]
21 UIKitCore                      0x1b68f5610 -[UIScene _invalidate]
22 UIKitCore                      0x1b74ceec4 -[UIWindowScene _invalidate]
23 UIKitCore                      0x1b72a2b20 -[UIApplication workspace:willDestroyScene:withTransitionContext:completion:]
24 UIKitCore                      0x1b6e64c10 -[UIApplicationSceneClientAgent scene:willInvalidateWithEvent:completion:]
25 FrontBoardServices             0x1b8331bdc -[FBSSceneImpl _callOutQueue_agent_willDestroyWithTransitionContext:completion:]
26 FrontBoardServices             0x1b8357b70 __84-[FBSWorkspaceScenesClient _queue_invalidateScene:withTransitionContext:completion:]_block_invoke_2
27 FrontBoardServices             0x1b833c0f8 -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:]
28 FrontBoardServices             0x1b83579e8 __84-[FBSWorkspaceScenesClient _queue_invalidateScene:withTransitionContext:completion:]_block_invoke
29 libdispatch.dylib              0x1b2f66184 _dispatch_client_callout
30 libdispatch.dylib              0x1b2f0f038 _dispatch_block_invoke_direct$VARIANT$mp
31 FrontBoardServices             0x1b837b540 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__
32 FrontBoardServices             0x1b837b20c -[FBSSerialQueue _queue_performNextIfPossible]
33 FrontBoardServices             0x1b837b734 -[FBSSerialQueue _performNextFromRunLoopSource]
34 CoreFoundation                 0x1b32167e0 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
35 CoreFoundation                 0x1b3216738 __CFRunLoopDoSource0
36 CoreFoundation                 0x1b3215ed0 __CFRunLoopDoSources0
37 CoreFoundation                 0x1b321101c __CFRunLoopRun
38 CoreFoundation                 0x1b32108bc CFRunLoopRunSpecific
39 GraphicsServices               0x1bd07c328 GSEventRunModal
40 UIKitCore                      0x1b72a66d4 UIApplicationMain
41 MyApp                           0x1050801cc main + 14 (main.m:14)
42 libdyld.dylib                  0x1b309b460 start

References Issue #55

The avoidingView was not moving back to the original position after "undo typing" click.

Basically, the problem is after the "undo typing" click the keyboardWillChangeFrameNotification observer will be called three times: 1 time: target to show the keyboard 2 time: target to hide the keyboard 3 time: target to show the keyboard

The third call will be executed bevor the "restore state" animation from the second call is finished. Therefore in the third call, all auto location are still saved in updatedConstraints & updatedConstraintConstants. So we need to wait for the animation to finish and then call didChange with the preserved notification object.