I’m fed up with this issue When I make any change ...
# compose-desktop
r
I’m fed up with this issue When I make any change to Coomposable function bodies which call this Composable and run to android my device AS doing something wrong and at runtime throwing this error
I’ve no chance except to use jetpack compose instead of jetbrains compose
o
to fix this issue we’ll need a reproducer, likely you have different versions of coil when compiling and running. Not sure if it’s related to Compose per se.
r
I’m using coil core lib and copied compose codes. It’s not related to this
The problem is originating from a expect/actual composable function
I’m declaring CoilImage Composable function in commonMain and implementing android/desktop parts differently
Every time when I encounter to this issue I have to uninstall my app from the device and rerun
i
Does expect/actual have default parameters? There is an issue with them
r
Yes it has. Is there a workaround to this issue?When I call this function I have to pass all param values?
I’ll move all my compose codes to android module
o
you can just avoid using default args in expect/actual and provide a common wrapper with default arguments
👍 1
r
It took me two days to resolve this issue
c
I didn't know you can use coil in compose for desktop. 🤔
r
@Colton Idle You can use it for android module for desktop you can use other code
s
What other code did you use for desktop?
r
@spierce7 I used ktor client to fetch images and called it inside LaunchedEffect where image state will be updated
I must make some optimizations later but now it’s not priority
@Igor Demin could you share the issue tracker?
i
The issue in compose-jb tracker And the issue in YouTrack (but the bug is probably somewhere in compose compiler) It seems the users will often encounter this, as Composable's often contain default parameters. I think we need to look at this before 1.0.0 🤔