I have a simple nav baed app. I push the tableviewcontroller that contains pulltorefresh, works as advertised. I pop back to previous view and trigger a memory warning in the simulator. Generally it crashes first try, sometimes second. Commenting out the svpulltorefresh fixes the crash when I trigger the memory warning in the same way. I think a message is being sent to a deallocated obj.

If one converts the associated sample into a navigation based application with pushing of multiple SVViewController.xib by first adding a button in xib and then pushing the same view controller with tapping of that button. When we go back by tapping on the back button then the memory is not released back. This is probably due to the dealloc of both the view controller as well as SVPullToRefresh is not being called. Also the latest version of SVPullToRefresh also gets crashed when the pull to refresh is in action and one goes back to previous view controller [pop action]

When the tableView's data source contains a few objects , in other words the data source can't fill full of the tableView then pull to refresh , it will trigger "Load more" and "Refresh" at the same time. http://youtu.be/ntza9pqUmn0

I followed the required steps to add the SVPullToRefreshView but it doesn't seems to work. I get following error.

-[UITableView addPullToRefreshWithActionHandler:]: unrecognized selector sent to instance

Any idea? Thanks

how can i add your amazing pulltorefresh to a webview? i use it with tableview and it works perfectly....but with webview no....teorically it is a uiview subclass... so?

Thanks for your work

Sam, nice work on this. One problem, which I've found in nearly all PTR implementations, is that you have a retain cycle. I updated the demo code to reference the SVPullToRefresh in a __block variable. Otherwise the controller gets retained when the block is copied, and it will never be released.

I also made the scrollView property weak instead of strong. The scroll view retains SVPullToRefresh in its subviews array. If SVPullToRefresh also retains the scrollView, neither will ever be released.

The problem is easy to reproduce in the Allocations instrument. Just tap the launch button, navigate back up, rinse, repeat. You'll see new instances SVController, SVPullToRefresh, and UITableView every time you launch the controller, which are never deallocated.

Added -addPullToRefreshWithActionHandler:position: which takes a SVPullToRefreshPosition as second parameter.

SVPullToRefreshPosition may be either:

• SVPullToRefreshPositionTop : pull to refresh from the top of the scroll view (the current behavior)
• SVPullToRefreshPositionBottom : pull to refresh from the bottom of the scroll view

-addPullToRefreshWithActionHandler: defaults on SVPullToRefreshTop, making this update fully backward compatible.

Example

[self.tableView addPullToRefreshWithActionHandler:^{
   // ...
} position:SVPullToRefreshPositionBottom];

will result in the following behavior

This update comes with two additional handlers. DragToLoad allows you to drag past the bottom content and trigger a refresh, similar to PullToRefresh. InfiniteScroll will automatically trigger the refresh when 80% of the content has been scrolled through. Additionally, you can set the sectionLoadLimit and the rowLoadLimit to tell your tableView how much content to load at a time. There is also a loadNextPortion method that will handle incrementing the loaded portions and refreshing your content for you; you just need to update your data source.

Considering everything else can be customized, I figured it would be nice to add support for setting a custom color for the UIActivityIndicatorView so that user's aren't constrained to either white or gray.

When the navigation controller pushes on a new controller, the previous view is removed from the hierarchy (but not released) and so willMoveToSuperview gets called. This means that when the user returns to the view, the pullToRefresh instance is re-created and doesn't function as expected.

My understanding is that an associated object marked "retain" will be released along with the owning object. If this is the case (and I could be mistaken), this pre-emptive removal of the views may be unnecessary.

I'm running this in iOS6 simulator in Xcode 4.5 GM

Every time the table to it's end, it will load data automatically, I think it's not should be. When table view to end, footer shows with label "Pull to load more...", and when people drag up then the indicator with label "loading..." shows, and load data. I think it's more friendly, I have work on for this for several hours and over my head. So I come here for your help, could you add the function? Thanks.

Swift Package Manager

• iOS: Open Xcode, File->Swift Packages, search input https://github.com/samvermette/SVPullToRefresh.git, and then select Version Up to Next Major 0.4 < .
• Or add dependencies in your Package.swift:

.package(url: "https://github.com/samvermette/SVPullToRefresh.git", .upToNextMajor(from: "0.4")),

Please git tag for this pull request.

Apparently default infinite scrolling view's activity indicator view does not show when enter trigger state. It only shows when enter loading state. This commit fix the problem by manually set hidden property to NO when updating state of infinite scrolling view.

Why we can't use direction: SVInfiniteScrollingDirectionTop in swift version 4.2? Can you help to fix error support the problem? I really need your library to load more chat.

Can I replace the image that is refreshed by the drop-down?Can I replace the image that is refreshed by the drop-down? Just like text, you can set the substitution

Can you use it for a wkwebview?

Thank you

I try this but don't work

webview?.scrollView.addPullToRefresh {
                                    self.getRequest(url_view: self.url_view)
}