Glide: Cannot setImageBitmap on a ImageView if the imageView is already set by Glide
Hey,
I am having this issue with Glide.
So if I use Glide to load a image into an imageView, i.e. Glide.with(..).load(..).into(imageView), I cannot do imageView.setImageBitmap(..) anymore. There is no exception thrown, but the imageView still displays the old image from Glide.
The workaround is to use Glide all the way, i.e., always use Glide...into(imageView). The imageView is correctly set everytime.
I am wondering if this is a known issue? I think Glide should not take away to Android's native setImageBitmap()?
Thanks!
Wei
eewwxac
All 5 comments
Glide doesn't necessarily take that method away, but Glide assumes that it's managing a view until you tell it not to. That means that if you start a load on a view, and then set a Bitmap on that view, Glide's load may then finish and replace the image with the one from Glide.
To stop Glide from managing the view, always call Glide.clear(View) before setting any resources.
sjudd
on 29 Apr 2015
you are awesome. Thank you Sam.
eewwxac
on 29 Apr 2015
Great, glad that answered your question!
sjudd
on 29 Apr 2015
Great!
fcaden2016
on 21 Feb 2017
and here i am pulling my hair off because of this problem
cimeng
on 28 Feb 2018
Related issues
billy2271
路
3Comments
ersen-osman
路
3Comments
Ncit
路
3Comments
Anton111111
路
3Comments
FooBarBacon
路
3Comments
Most helpful comment
Glide doesn't necessarily take that method away, but Glide assumes that it's managing a view until you tell it not to. That means that if you start a load on a view, and then set a Bitmap on that view, Glide's load may then finish and replace the image with the one from Glide.
To stop Glide from managing the view, always call
Glide.clear(View)before setting any resources.