iOS 11 offset in tableView

Question

iOS 11 offset in tableView

josepbordesjove opened this issue 7 years ago · 11 comments

josepbordesjove commented 7 years ago

I've read and understood the Contributing guidelines and have done my best effort to follow them.
I've read and agree to the Code of Conduct.
I've searched for any related issues and avoided creating a duplicate issue.

Description

With the brand new iOS 11, there appears an offset on the table view of the SlackTextViewController.

Reproducible in:

This is reproducible in the sample project.
SlackTextViewController version: 1.9.5
iOS version(s): iOS 11
Device(s): Anyone (I attach an screen shot of iPhone 7 Plus)

Steps to reproduce:

Download the sample project.
Run it with the iOS 11 simulator and iOS 10.3 simulator (using Xcode 9)

Expected result:

The table should appear without any content offset (iPhone 7 Plus, iOS 10.3.1)

Actual result:

The table has offset (iPhone 7 Plus, iOS 11)

Thank you for your help!

Josep

Answer 1 · 2017-09-28T15:09:59.000Z

I imagine this is because of the change in iOS 11 where it no longer automatically adjusts the scroll view's content inset to accommodate top/bottom bars, by default.

Answer 2 · 2017-09-28T15:48:35.000Z

Thank you, that solved my problem! For others trying to solve the same issue, I found the solution on the wwdc video, https://developer.apple.com/videos/play/wwdc2017/204/.

 if #available(iOS 11.0, *) {
    tableView.contentInsetAdjustmentBehavior = .never
}

Answer 3 · 2017-09-28T17:12:52.000Z

It seems like a better fix is automaticallyAdjustsScrollViewInsets = false which is backwards compatible, being discussed in #531

@josepbordesjove mind try that up, and maybe push a PR fixing it for both, iOS 11 and iOS 10?

Answer 4 · 2017-09-29T07:18:59.000Z

@dzenbot, thank you, I am gooing to do that and make a PR!

Answer 5 · 2017-10-21T09:37:19.000Z

@josepbordesjove's solution above works. Using automaticallyAdjustsScrollViewInsets = false as @dzenbot suggests does not work for me.

Answer 6 · 2017-11-02T05:42:42.000Z

does not work for me either

Answer 7 · 2017-11-02T08:07:17.000Z

@yarodevuci it should be solved because the PR is already merged, if not, maybe your problem is different, anyways try to upload your pods.

Answer 8 · 2017-11-02T08:09:51.000Z

@josepbordesjove in version: 1.9.6?

Answer 9 · 2017-11-02T08:14:37.000Z

@yarodevuci yes!

Answer 10 · 2017-11-02T08:17:40.000Z

@josepbordesjove I am updated, but I still have the issue, any ideas what else to check?

Answer 11 · 2017-11-02T08:25:52.000Z

@yarodevuci Can you upload a screenshot of the issue? But I'd copy the code into the viewDidLoad, if the new release does not solve your problems. Also I'd try to delete the Pods and Podfile.lock and install them again.