*Edit: Solved - My misunderstanding between `sharedLib` and `klib` publishing (which works* :white_c...

# compose-ios

[darkmoon_uk]

Edit: Solved - My misunderstanding between sharedLib and klib publishing (which works ✅*)*

It it still unsupported to build a sharedLib binary for iOS to provide public @Composable functions? 🤔
This would mean we can't have K Compose/iOS Component libraries - pretty vanilla requirement don't you think? 🤯
Whenever I try I get the dreaded No file for error (as discussed here two years ago), e.g:

Compilation failed: No file for org.chrishatton.timeline.presentation.view/TimelineView|TimelineView(){}[0]

...I'm using Kotlin 2.0.0 with Compose Multiplatform 1.6.10 .
Tried a number of things including disabling cache, but no dice 🤷

[Ivan Matkov]

Could you please clarify the use case? What do you want to achieve?

Composable functions aren't exposed to ObjC/Swift because you cannot (and shouldn't) call them outside of composable context

[darkmoon_uk]

Oh! I just realised my misunderstanding. I was conflating sharedLib binary definition with being able to publish klib Maven artifact.

[darkmoon_uk]

That's native dylib output I now realise; binaries { sharedLib {} } can be removed and I can still build & publish iOS Maven Artifacts.

[Oleksandr Karpovich [JB]]

is TimelineView an expect/actual fun by chance?

[darkmoon_uk]

No it is not `expect`ed in this case; and to rule out complexities I reduced it to only @Composable fun TimelineView(): Unit {} but still got the error with binaries { sharedLib {} } present.

[darkmoon_uk]

I'm unblocked, but the No File error still strikes me as a rough edge; a nice warning like "Publishing public @Composable functions is unsupported for iOS native .dylib or .framework binaries" would be less confusing, if possible 🙂