Replies: 1 comment
-
Ok, so I found the following: #153. Note: I am using the load() method. It still doesn't make sense to me as when the RecyclerView detaches a child view, it is not necessarily meant for loading the same item anymore. The other argument about fragments I don't fully understand which aspect of Fragments you are talking about. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First off, I can't upgrade because it requires a newer version of kotlin which I can't bump up. I had attempted searching through the git history since 2.2.2 to see if it was ever fixed but fell short.
I have code where the ImageView is in a RecyclerView where sometimes images will be loaded via Coil and sometimes via other methods depending on what it is. For simplicity, we can assume the view for each item is just an ImageView. What I'm experiencing is when something is first loaded with Coil and then the view gets recycled and used for another item which is loading the icon via another method, Coil will overwrite its image onto the ImageView even though it should no longer be associated w/ it.
I guess my question is, is this expected? I would assume the View getting recycled would cause coil to detach itself from the view. The only thing I can think of doing is calling dispose() before using any other method, however, this was never required with other image loading libraries I had used (Picasso/Glide). On top of this, it breaks the abstraction in use in the application.
Beta Was this translation helpful? Give feedback.
All reactions