-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Swift 3 Ui Freeze with show progress on working with Alamofire #99
Comments
This may not be limited to alamofire. I am having UI unresponsiveness, when the complete block of KVNProgress.dismiss(completion: {}) is fired. If I dismiss it with KVNProgress.dismiss() there does not seem to be an issue. I am hitting the network when this happens so maybe it is related to that. But I am not using Alamofire anywhere in the app. |
I'm also experiencing seemingly random app freezes since migrating to Swift 3, but some of my users are experiencing this pretty often. I'm using KVNProgress heavily, so I will try to reproduce as you described. |
So I removed KVNProgress from my project. No more complaints since then, so it is definitly an issue of this library. I use KVNProgress mostly to show success or error. |
I'm narrowing down the cause of this bug and I think it actually is a result of calling dismiss() multiple times, or more specifically calling dismiss() when there is no kvnprogressview visible. |
👍 |
I was able to fixed this issue (in my case) by adding a
|
Today i already fixed by check isVisible before show other KVNProgress example
after that before recall just check previous.
|
I created KVNManager to wrapped KNV library to manage it before show or dismiss.
|
Issue still exist with alamofire . Can anyone help on this . |
Call
KVNProgress.show(0.0, status: "Logging...")
in main threadthen in alamofire
request.responseJSON { (response:DataResponse<Any>) in
call
DispatchQueue.main.async { KVNProgress.showSuccess() }
or
KVNProgress.showSuccess()
The text was updated successfully, but these errors were encountered: