我发现@DK_是我开始使用的解决方案。然而，假设scrollView覆盖了整个视图。我不是这样的。我只想要一个滚动视图，以防键盘覆盖了登录屏幕上的下文本字段。因此，我的内容视图与滚动视图大小相同，比主视图小。

它也没有考虑到景观，这是我开始遇到麻烦的地方。玩了几天后，这是我的键盘显示：方法。

- (void)keyboardWasShown:(NSNotification*)aNotification
{
    // A lot of the inspiration for this code came from http://stackoverflow.com/a/4837510/594602
    CGFloat height = 0;
    NSDictionary* info = [aNotification userInfo];

    CGRect kbFrameRect = [[info objectForKey:UIKeyboardFrameEndUserInfoKey] CGRectValue];
    CGRect kbBoundsRect = [self.view convertRect:kbFrameRect fromView:nil]; // Convert frame from window to view coordinates.

    CGRect scrollRect = scrollView.frame;
    CGRect intersect = CGRectIntersection(kbBoundsRect, scrollRect);

    if (!CGRectIsNull(intersect))
    {
        height = intersect.size.height;
        UIEdgeInsets contentInsets = UIEdgeInsetsMake(0.0, 0.0, height, 0.0);
        scrollView.contentInset = contentInsets;
        scrollView.scrollIndicatorInsets = contentInsets;
    }

    // Figure out what the view rectangle is for the scrollView
    CGPoint contentOffset = scrollView.contentOffset;
    CGRect visibleRect = CGRectOffset(scrollRect, contentOffset.x, contentOffset.y);    // I'm not 100% sure if this is needed/right. My scrollView was always at the top in testing.
    visibleRect.size.height -= height;
    CGRect activeRect = activeField.frame;

    if (!CGRectContainsRect(visibleRect, activeRect))
    {
        [self.scrollView scrollRectToVisible:activeField.frame animated:YES];
    }
}

我在使用自动布局时也遇到了一些困难。如果我没有正确完成布局，我就没有得到预期的滚动效果。有一件事让生活变得更加简单，那就是将所有要滚动的项目放在一个视图中，并将其作为滚动视图中的唯一项目。我把这个单一视图称为“内容视图”。

我认为关键部分是内容视图有一个设定的宽度和高度。这使得滚动视图能够准确地知道需要处理多少内容。这与通常的布局有点不同。通常情况下，视图会尽量占据更多空间。对于滚动视图的内容，您试图使视图尽可能地限制自己。内容视图允许您停止此操作。所以我给了我248的高度，并使用320的标准屏幕宽度作为我的宽度。

最终对我有用的布局如下：

滚动视图到超级视图：基本上我给了顶部、左侧和右侧的约束。水平空间-视图-滚动视图（0）垂直空间-视图-滚动视图（0）水平空间-滚动视图-视图（0）滚动视图高度：我将滚动视图设置为恒定高度。我不知道这是否真的有必要，但它有滚动视图本身的界限。高度-（248）-滚动视图滚动视图的内容视图：我给了所有方面的常量，顶部、左侧、底部和右侧。垂直空间-视图-滚动视图（0）垂直空间-滚动视图-视图（0）水平空间-视图-滚动视图（0）水平空间-滚动视图-视图（0）内容视图的维度。高度-（248）-视图宽度-（320）-视图

已经有很多答案了，但上面的解决方案仍然没有一个具备“完美”无bug、向后兼容和无闪烁动画所需的所有花哨定位功能。（在一起设置帧/边界和contentOffset动画时出错，界面方向不同，iPad分割键盘等）让我分享我的解决方案：（假设您已设置UIKeyboardWill（显示|隐藏）通知）

// Called when UIKeyboardWillShowNotification is sent
- (void)keyboardWillShow:(NSNotification*)notification
{
    // if we have no view or are not visible in any window, we don't care
    if (!self.isViewLoaded || !self.view.window) {
        return;
    }

    NSDictionary *userInfo = [notification userInfo];

    CGRect keyboardFrameInWindow;
    [[userInfo objectForKey:UIKeyboardFrameEndUserInfoKey] getValue:&keyboardFrameInWindow];

    // the keyboard frame is specified in window-level coordinates. this calculates the frame as if it were a subview of our view, making it a sibling of the scroll view
    CGRect keyboardFrameInView = [self.view convertRect:keyboardFrameInWindow fromView:nil];

    CGRect scrollViewKeyboardIntersection = CGRectIntersection(_scrollView.frame, keyboardFrameInView);
    UIEdgeInsets newContentInsets = UIEdgeInsetsMake(0, 0, scrollViewKeyboardIntersection.size.height, 0);

    // this is an old animation method, but the only one that retains compaitiblity between parameters (duration, curve) and the values contained in the userInfo-Dictionary.
    [UIView beginAnimations:nil context:NULL];
    [UIView setAnimationDuration:[[userInfo objectForKey:UIKeyboardAnimationDurationUserInfoKey] doubleValue]];
    [UIView setAnimationCurve:[[userInfo objectForKey:UIKeyboardAnimationCurveUserInfoKey] intValue]];

    _scrollView.contentInset = newContentInsets;
    _scrollView.scrollIndicatorInsets = newContentInsets;

    /*
     * Depending on visual layout, _focusedControl should either be the input field (UITextField,..) or another element
     * that should be visible, e.g. a purchase button below an amount text field
     * it makes sense to set _focusedControl in delegates like -textFieldShouldBeginEditing: if you have multiple input fields
     */
    if (_focusedControl) {
        CGRect controlFrameInScrollView = [_scrollView convertRect:_focusedControl.bounds fromView:_focusedControl]; // if the control is a deep in the hierarchy below the scroll view, this will calculate the frame as if it were a direct subview
        controlFrameInScrollView = CGRectInset(controlFrameInScrollView, 0, -10); // replace 10 with any nice visual offset between control and keyboard or control and top of the scroll view.

        CGFloat controlVisualOffsetToTopOfScrollview = controlFrameInScrollView.origin.y - _scrollView.contentOffset.y;
        CGFloat controlVisualBottom = controlVisualOffsetToTopOfScrollview + controlFrameInScrollView.size.height;

        // this is the visible part of the scroll view that is not hidden by the keyboard
        CGFloat scrollViewVisibleHeight = _scrollView.frame.size.height - scrollViewKeyboardIntersection.size.height;

        if (controlVisualBottom > scrollViewVisibleHeight) { // check if the keyboard will hide the control in question
            // scroll up until the control is in place
            CGPoint newContentOffset = _scrollView.contentOffset;
            newContentOffset.y += (controlVisualBottom - scrollViewVisibleHeight);

            // make sure we don't set an impossible offset caused by the "nice visual offset"
            // if a control is at the bottom of the scroll view, it will end up just above the keyboard to eliminate scrolling inconsistencies
            newContentOffset.y = MIN(newContentOffset.y, _scrollView.contentSize.height - scrollViewVisibleHeight);

            [_scrollView setContentOffset:newContentOffset animated:NO]; // animated:NO because we have created our own animation context around this code
        } else if (controlFrameInScrollView.origin.y < _scrollView.contentOffset.y) {
            // if the control is not fully visible, make it so (useful if the user taps on a partially visible input field
            CGPoint newContentOffset = _scrollView.contentOffset;
            newContentOffset.y = controlFrameInScrollView.origin.y;

            [_scrollView setContentOffset:newContentOffset animated:NO]; // animated:NO because we have created our own animation context around this code
        }
    }

    [UIView commitAnimations];
}


// Called when the UIKeyboardWillHideNotification is sent
- (void)keyboardWillHide:(NSNotification*)notification
{
    // if we have no view or are not visible in any window, we don't care
    if (!self.isViewLoaded || !self.view.window) {
        return;
    }

    NSDictionary *userInfo = notification.userInfo;

    [UIView beginAnimations:nil context:NULL];
    [UIView setAnimationDuration:[[userInfo valueForKey:UIKeyboardAnimationDurationUserInfoKey] doubleValue]];
    [UIView setAnimationCurve:[[userInfo valueForKey:UIKeyboardAnimationCurveUserInfoKey] intValue]];

    // undo all that keyboardWillShow-magic
    // the scroll view will adjust its contentOffset apropriately
    _scrollView.contentInset = UIEdgeInsetsZero;
    _scrollView.scrollIndicatorInsets = UIEdgeInsetsZero;

    [UIView commitAnimations];
}

非常轻量级的解决方案可以使用KeyboardAnimator。

项目获得了示例实现，文档编制仍在进行中。。。

适当用法：它具有UITextField和UITextView的特定实现

限制：：它完全基于objective-c，swift版本将很快推出。

-(BOOL) textFieldShouldBeginEditing:(UITextField *)textField {

  [self slideUp];
   return YES;
}

-(BOOL) textFieldShouldEndEditing:(UITextField *)textField {

    [self slideDown];
   return YES;
}

#pragma mark - Slide Up and Down animation

- (void) slideUp {
    [UIView beginAnimations:nil context:nil];
    layoutView.frame = CGRectMake(0.0, -70.0, layoutView.frame.size.width, layoutView.frame.size.height);

    [UIView commitAnimations];
}


- (void) slideDown {
    [UIView beginAnimations:nil context:nil];
    [UIView setAnimationDelay: 0.01]; 
    layoutView.frame = CGRectMake(0.0, 0.0, layoutView.frame.size.width, layoutView.frame.size.height);
    [UIView commitAnimations];
}

https://github.com/michaeltyson/TPKeyboardAvoiding下载此文件并添加自定义类，因为它将在您的表视图中管理所有内容，您无需执行任何操作。它有很多选项，你也可以为其他人查看，这是你需要避免使用键盘的全部

一个更为优雅的解决方案是使用UIView子类（虽然这并不总是合适的），并在父帧更改时重新计算所有子视图（并且要聪明：只有在新帧大小发生更改时才重新计算它们，即在重写setFrame和调用[super setFrame:frame_]之前使用CGRectEqualToRect来比较新帧）。唯一的缺点是，您打算使用的UIViewController可能应该监听键盘事件（或者，您可以在UIView本身中进行监听，以方便封装）。但只有UIKeyboardWillShowNotification和UIKeyboard WillHideNotification。这只是为了让它看起来平滑（如果你等待CG调用它，你会得到一个波涛汹涌的时刻）。

无论如何，这有一个优点，那就是构建一个做正确事情的UIView子类。

天真的实现是重写drawRect:（不要），更好的方法是只使用layoutSubviews（然后在UIViewController中，或者在为显示或隐藏调用的SINGLE方法中调用[view setNeedsLayout]）。

此解决方案摆脱了硬编码键盘偏移（如果它们不在拆分等中，则会发生变化），还意味着您的视图可以是许多其他视图的子视图，并且仍然可以正确响应。

除非没有其他解决方案，否则不要硬编码这样的东西。如果你做得对，操作系统会给你足够的信息，你只需要智能地重新绘制（基于你的新帧大小）。这要干净得多，而且是你应该做的事情。（不过，可能还有更好的方法。）

干杯