App crashes when using GlideImage with error after onResume about accompanist HOT 7 CLOSED

I've just tried this locally and I can't reproduce. Do you have a larger runnable reproducing case?

from accompanist.

I created a new repo with the issue demonstrated

from accompanist.

Thanks, I can repro but I don't really understand what's triggering it. I think what is happening is that Glide is re-executing the request whenever the host ComposeView is attached/detached.

To be honest I'm tempted to kill the Glide and Picasso libraries. Glide has a lot implicit functionality built on top of views which doesn't necessarily make sense for Compose, and Glide hasn't been updated in years.

Compose is built upon Kotlin and Coroutines, so I think it makes sense to only support Coil in the future.

from accompanist.

Ohh I see, If that's the case kill it, anyway thanks for the great library 😊

from accompanist.

@DavidIbrahim @chrisbanes any workaround or quick fix we can use without updating the lib or migrating to coil?

from accompanist.

Had a look at this today, and yep it's due to Glide doing all sorts of implicit automatic behavior that we no longer want.

As a workaround for now, you can do: val glide = Glide.with(LocalContext.current.applicationContext). Then either provide it to each GlideImage(), or use the LocalRequestManager composition local. See here for more info.

from accompanist.

Thanks @chrisbanes 😃

from accompanist.