-
Notifications
You must be signed in to change notification settings - Fork 89
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
Bugs #7
Comments
This is very weird. By second run, do you mean a build and run second time, or something else? |
By second run I meant as if I ran the same start/update/reveal cycle once again on the same image view. |
Ah, ok. Got it. I think we can fix this by doing some more cleanup at the end of reveal. (Resetting progress back to 0, possibly removing from superview) I'll take a look at this over the weekend. |
@rounak thank you! I had something like that in mind and I tried to remove view from superview but I guess it needs more thorough clean up. |
There are still similar problems in the list when multiplexing |
I have the same issue, what is the workaround? |
@pronebird I have the same issue, what is the workaround? |
I have the same issue,, |
@rounak @hyunwoo3008 did you resolved this issue ?? if yes, please tell me |
pod try RJImageLoader
opens broken project.I made a small video: http://cl.ly/1y0G1p050o0M. I think the problem is in SDWebImage:
I posted couple of issues in SDWebImage related to this problem. SDWebImage/SDWebImage#1090
Since SDWebImage is a wreck, we can avoid completion handler and run all animations in progress block:
But then it's all broken after I run it twice, see video: http://cl.ly/2U192i321D1N
The text was updated successfully, but these errors were encountered: