Prefer Large Titles and RefreshControl not working well

Question

I am using this tutorial to implement a pull-to-refresh behavior with the RefreshControl. I am using a Navigation Bar. When using normal titles everything works good. But, when using "Prefer big titles" it doesn't work correctly as you can see in the following videos. Anyone knows why? The only change between videos is the storyboard check on "Prefer Large Titles".

Does this help? https://stackoverflow.com/a/48347770/341994 – matt Jun 05 '18 at 20:27 — matt, Jun 05 '18 at 20:27

Bruno Cunha · Answer 1 · 2019-02-11T17:05:41.553

48

I'm having the same problem, and none of the other answers worked for me.

I realised that changing the table view top constraint from the safe area to the superview fixed that strange spinning bug.

Also, make sure the constant value for this constraint is 0 .

edited Feb 11 '19 at 17:05

answered Feb 11 '19 at 11:31

Bruno Cunha

1,680
1
17
15

3

Was struggling since morning, this is the only solution that worked for me(iOS 12.1). Thanks! – vivek takrani Mar 23 '19 at 12:39
4

Worked for me too, got 1 week to find the solution. Thanks! – articga Apr 04 '19 at 19:05
3

Thanks mate, it worked for me too! I had this bug for about a year – Stoyan Feb 13 '20 at 05:40
4

combine it with: tableView.contentInsetAdjustmentBehavior = .always – Trzy Gracje Mar 27 '20 at 14:49
this issue still exists – NMaks Jul 18 '22 at 05:13
1

I love you man <3 – timetraveler90 Sep 20 '22 at 11:36

score 22 · Accepted Answer · answered Jun 06 '18 at 12:58

22

At the end what worked for me was:

In order to fix the RefreshControl progress bar disappearing bug with large titles:
```
self.extendedLayoutIncludesOpaqueBars = true
```

In order to fix the list offset after refreshcontrol.endRefreshing():

let top = self.tableView.adjustedContentInset.top
let y = self.refreshControl!.frame.maxY + top
self.tableView.setContentOffset(CGPoint(x: 0, y: -y), animated:true)

answered Jun 06 '18 at 12:58

Damia Fuentes

5,308
6
33
65

If you have opaque tab bar and the self.extendedLayoutIncludesOpaqueBars = true makes everything go under the tab bar and you don't want this behavior then you can add 'self.edgesForExtendedLayout = UIRectEdge.top' – Oleg Sherman Jan 21 '19 at 07:49
First part helped me! – Sunkas Nov 12 '19 at 06:59
Check if you have any missing call of tableView.reloadData() before fixing the list offset, e.g. if you update tableHeaderView, you should call reloadData() immediately after it. – bojanb89 Jan 08 '21 at 12:02

score 8 · Answer 3 · answered Sep 24 '18 at 22:28

8

If you were using tableView.tableHeaderView = refreshControl or tableView.addSubView(refreshControl) you should try using tableView.refreshControl = refreshControl

answered Sep 24 '18 at 22:28

atish vishwakarma

201
3
5

Luke Pearce · Answer 4 · 2019-04-08T00:07:56.377

4

It seems there are a lot of different causes that could make this happen, for me I had a TableView embedded within a ViewController. I set the top layout guide of the tableview to the superview with 0. After all of that still nothing until I wrapped my RefreshControl end editing in a delayed block:

DispatchQueue.main.async {
   if self.refreshControl.isRefreshing {
       DispatchQueue.main.asyncAfter(deadline: .now() + 1.0, execute: {
            self.refreshControl.endRefreshing()
       })
   }
}

edited Apr 08 '19 at 00:07

answered Apr 07 '19 at 23:56

Luke Pearce

133
1
3

Sadly, I had to go with this solution which does feel a bit hacky. I did get away with reducing + 1.0 down to + 0.2 – Sherwin Zadeh Mar 26 '20 at 01:09

score 3 · Answer 5 · answered Mar 27 '20 at 14:47

3

The only working solution for me is combining Bruno's suggestion with this line of code:

tableView.contentInsetAdjustmentBehavior = .always

answered Mar 27 '20 at 14:47

Trzy Gracje

2,969
4
20
24

1

Thank you! Without this line of code, Bruno's suggestion causes an issue with `UIScrollView.scrollsToTop`. (Note: You can also set this in IB in the Size Inspector pane.) – Arseniy Banayev Nov 11 '20 at 05:32

score 2 · Answer 6 · answered Mar 12 '20 at 13:05

2

I've faced the same problem. Call refreshControl endRefreshing before calling further API.

refreshControl.addTarget(controller, action: #selector(refreshData(_:)), for: .valueChanged)

@objc func refreshData(_ refreshControl: UIRefreshControl) {
        refreshControl.endRefreshing()
        self.model.loadAPICall {
            self.tableView.reloadData()
        }
    }

answered Mar 12 '20 at 13:05

Balaji G

77
5

I did use OperationQueue and dependency between operations and it works good – NMaks Jul 18 '22 at 06:24

score 0 · Answer 7 · answered Jun 26 '19 at 15:17

The only solution that worked for me using XIBs was Bruno's one: https://stackoverflow.com/a/54629641/2178888

However I did not want to use a XIB. I struggled a lot trying to make this work by code using AutoLayout.

I finally found a solution that works:

    override func loadView() {
        super.loadView()
        let tableView = UITableView()
        //configure tableView
        self.view = tableView
    }

Asi Givati · Answer 8 · 2020-01-16T12:00:28.723

0

I had this issue too, and i fixed it by embedded my scrollView (or tableView \ collectionView) inside stackView, and it's important that this stackView's top constraint will not be attached to the safeArea view (all the other constraints can). the top constraint should be connect to it's superview or to other view.

edited Jan 16 '20 at 12:00

answered Jan 15 '20 at 11:39

Asi Givati

1,348
1
15
31

score 0 · Answer 9 · answered Aug 05 '20 at 12:25

0

I was facing the same issue for very long, the only working solution for me was adding refresh control to the background view of tableview.

tableView.backgroundView = refreshControl

answered Aug 05 '20 at 12:25

Karan Bhatia

807
1
8
16

score 0 · Answer 10 · answered Nov 30 '20 at 16:21

Short Answer

I fixed this by delaying calling to API until my collection view ends decelerating

Long Answer

I notice that the issue happens when refresh control ends refreshing while the collection view is still moving up to its original position. Therefore, I delay making API call until my collection view stops moving a.k.a ends decelerating. Here's a step by step:

Follow Bruno's suggestion
If you set your navigation bar's translucent value to false (navigationBar.isTranslucent = false), then you will have to set extendedLayoutIncludesOpaqueBars = true on your view controller. Otherwise, skip this.
Delay api call. Since I'm using RxSwift, here's how I do it.

collectionView.rx.didEndDecelerating
    .map { [unowned self] _ in self.refreshControl.isRefreshing }
    .filter { $0 == true }
    .subscribe(onNext: { _ in
        // make api call
    })
    .disposed(by: disposeBag)

After API completes, call to

refreshControl.endRefreshing()

Caveat

Do note that since we delay API call, it means that this whole pull-to-refresh process is not as quick as it could have been done without the delay.

score 0 · Answer 11 · answered Aug 30 '22 at 13:36

0

Unfortunately, no advice helped. But I found a solution that helped me. Setting the transparency of the navigation bar helped.enter image description here

answered Aug 30 '22 at 13:36

Сергей Верховский

11
2

score -1 · Answer 12 · answered Jan 05 '20 at 01:28

-1

Problem can be solved if add tableview or scroll view as root view in UIViewController hierarchy (like in UITableViewController)

override func loadView() {
    view = customView
}

where customView is UITableView or UICollectionView

answered Jan 05 '20 at 01:28

Andreichev Michail

1

Prefer Large Titles and RefreshControl not working well

12 Answers12

Short Answer

Long Answer

Caveat

Linked