UITextView cursor not positioning properly when editing in iOS 7. Why?

Question

That yellow box above is an editable UITextView that is currently being edited (is first responder). But you probably couldn't tell right? Because there is no cursor. But there is... It's that small blue dot in the bottom left of the yellow textView. It's slightly below the textViews bottom border. So if I keep going to a new line, or pressing enter, the text will move up as it naturally should. But the cursor is never "level", or right above the UITextView's bottom border. It's always just barely poking out of the bottom, a couple points below the border.

Why? This wasn't a problem in iOS 6. Any way to fix this?

Answer 1

this bug is in iOS 7.0 you can solve this by modifying textView delegate method.

try below code

- (void)textViewDidChange:(UITextView *)textView {     CGRect line = [textView caretRectForPosition:         textView.selectedTextRange.start];     CGFloat overflow = line.origin.y + line.size.height         - ( textView.contentOffset.y + textView.bounds.size.height         - textView.contentInset.bottom - textView.contentInset.top );     if ( overflow > 0 ) {     // We are at the bottom of the visible text and introduced a line feed, scroll down (iOS 7 does not do it)     // Scroll caret to visible area         CGPoint offset = textView.contentOffset;         offset.y += overflow + 7; // leave 7 pixels margin     // Cannot animate with setContentOffset:animated: or caret will not appear         [UIView animateWithDuration:.2 animations:^{             [textView setContentOffset:offset];         }];     } } 

your problem will solved.

Answer 2

If you're in a navigation controller scenario, I think this is actually a result of a property that was introduced in iOS 7: automaticallyAdjustsScrollViewInsets (see iOS 7 transition guide)

This defaults to YES, and will try to get clever with the UITextView (which is itself a scroll view) by adjusting the scroll offset for the height of the navigation controller.

The solution is therefore to set this property to NO in your viewDidLoad (being careful not to call it on iOS 6 since it's only available as of iOS 7).