Colin White

@slees-figma Is there any update on this? We'd like to use Code Connect (especially with the new MCP announcement), but this is a blocking issue for us.

Which version of Compose are you using? I wonder if it could be related to https://github.com/coil-kt/coil/issues/2771.

Hi folks I took a look at this and opened an issue on the [Coil tracker to track](https://github.com/coil-kt/coil/issues/1910). I'm not 100% sure if this is a Coil issue, a Paparazzi...

@hunglvv Coil [does include](https://github.com/coil-kt/coil/blob/main/coil-core/src/jvmCommonMain/kotlin/coil3/fetch/JarFileFetcher.kt) a `jar:file` fetcher on JVM. For wasmJS I'm pretty sure it packages its assets as web resources - not JAR entries?

To work around this issue, wrap your `ImageRequest` in a `remember`: ```kotlin val context = LocalPlatformContext.current val painter = rememberAsyncImagePainter( model = remember(context) { ImageRequest.Builder(context) .data("https://example.com/image") .crossfade(true) .build() }, imageLoader...

Requested Copilot as well as I want to kick the tires on it 😅

@PMARZV Could you open a separate enhancement request for that please?

Yep this isn't ideal. Fortunately it only occurs with an implicit `ImageRequest.Builder` receiver which is only used with `ImageView.load` - not Compose. I don't think we can rename `error` as...

Thanks, looks like this is a side effect of using `ImageDecoder` for newer API levels in Coil 3. When I force using the old `BitmapFactory` implementation it's consistent with Coil...

@bashpsk What exception do you get in the `AsyncImage(onError = {})` callback? Please include a small project that reproduces the issue as I'm not able to reproduce the issue with...