[Coil 3] VectorDrawable @Preview doesn't work

[OKatrych]

Describe the bug
After the last fix, the AsyncImage @Preview render started working only for raster images. If we put a VectorDrawable as an argument, it doesn't render the preview image.

To Reproduce
Here, in this case, eu_flag is WebP and fi_flag is XML:

Here is a preview:

And if I move fi_flag to be shown before the eu_flag, it fails to render both of them:

Version
3.0.0-alpha10

[colinrtwhite]

Interesting I wonder if we need to add some special handling for XML drawables inside the preview environment. The current implementation delegates to the same way we load them on a real device so we can ideally keep the loading logic consistent. We probably need to add special handling for this case in here.

[tgyuuAn]

@OKatrych

I'd like to take on this issue, but I couldn't reproduce it.

In my case, when I tried rendering fi_flag with svg vector drawable and eu_flag with webp in version 3.0.0 alpha 10, both came out fine.

Could you please tell me more about the issue?

(This is the result after emptying the caching and checking.)

[colinrtwhite]

@tgyuuAn Thanks for taking a look! I was able to repro the bug here on Android Studio Ladybug 2024.2.1 Patch 1 and Ladybug Feature Drop 2024.2.2 Canary 8 on Mac Sequoia 15.1.

[tgyuuAn]

@tgyuuAn봐주셔서 감사합니다! Android Studio Ladybug 2024.2.1 Patch 1과 Ladybug Feature Drop 2024.2.2 Canary 8 on Mac Sequoia 15.1에서 버그 를 재현할 수 있었습니다.

Thank you !!! 🙃🙃

[colinrtwhite]

@tgyuuAn Were you able to take a look at this issue?

[tgyuuAn]

@tgyuuAn Were you able to take a look at this issue?

Unfortunately, I wasn't able to reproduce the issue, and it seems that there are quite a few bugs in the Ladybug version. I'm looking forward to the next version being released soon...

[SandraDupreDNA]

I have the same issue: I need to wrap all direct vector resources in a Drawable to see them in Preview or in Paparazzi screenshots. Also I can reproduce the bug on LadyBug 2024.2.1 Patch 2 and Meerkat 2024.3.1 Canary 2, so I'm not sure the issue will be fixed with the next Android Studio release.