Swift: Pull to refresh is too sensitive - ios

Question

am not too sure if anyone has encountered this issue, but it seems that my refreshControl is too sensitive. In my implementation, I attempt to do a pull to refresh and the code executes even before I see the refreshControl spinning.
Is there something wrong I'm doing?
My implementation so far.
//At initiation
lazy var refreshControl: UIRefreshControl = {
let rc = UIRefreshControl()
rc.tintColor = .white
rc.addTarget(self, action: #selector(refreshControlDidRefresh), for: .valueChanged)
return rc
}()
//At viewDidLoad(), I call a function setupViews()
func setupViews() {
view.backgroundColor = .white
view.addSubview(tableView)
tableView.topAnchor.constraint(equalTo: view.topAnchor).isActive = true
tableView.leadingAnchor.constraint(equalTo: view.safeAreaLayoutGuide.leadingAnchor).isActive = true
tableView.trailingAnchor.constraint(equalTo: view.safeAreaLayoutGuide.trailingAnchor).isActive = true
tableView.bottomAnchor.constraint(equalTo: view.safeAreaLayoutGuide.bottomAnchor).isActive = true
tableView.register(GossipsTableViewCell.self, forCellReuseIdentifier: "gossipCell")
tableView.tableHeaderView = emptyTableViewHeader()
tableView.refreshControl = refreshControl
}
#objc func refreshControlDidRefresh() {
DispatchQueue.main.async {
self.gossips.removeAll()
self.tableView.reloadData()
}
getData()
}
func getData() {
FirebaseClient.shared.fetchAllGossips { (results, error) in
if let error = error {
print(error.localizedDescription)
} else if let results = results {
self.gossips = results.sorted(by: { (gossip1, gossip2) -> Bool in
guard
let gossip1Timestamp = gossip1.timestamp,
let gossip2Timestamp = gossip2.timestamp else {
return false
}
return gossip1Timestamp > gossip2Timestamp
})
self.filterGossips()
DispatchQueue.main.async {
if self.refreshControl.isRefreshing {
self.refreshControl.endRefreshing()
}
if JustHUD.shared.isActive {
JustHUD.shared.hide()
}
var indexPaths = [IndexPath]()
for (index, _) in self.gossips.enumerated() {
let indexPath = IndexPath(row: index, section: 0)
indexPaths.append(indexPath)
}
self.tableView.insertRows(at: indexPaths, with: .automatic)
self.segmentedControl.isUserInteractionEnabled = true
}
}
}
}
You may see the results here. As I attempt to pull down, the refresh gets executed even before I start to see the refreshControl being drawn. Is there anything I'm missing out?

Answer 1

You are doing everything correctly, this is the default behaviour of pull to refresh control. If you want it to act differently, try a 3rd-part solution or remove the control and implement your own logic in scrollViewDidScroll.