Anybody publishing a library as a cocoapod? Wondering if there are any obvious issues. I’m aware that you can’t include multiple. This is for a client that wants to distribute their library to developers for use in native apps. Most would just be importing the framework on iOS. If somebody wanted to use it as a multiplatform library, that would be available as well.

We do it internally. If you want it to link against other pods, it's tricky (but doable). Main thing though is just ensuring you put out a fat framework with the dsym. Once you have that, it's like any other

vendored_framework

(in podspec lingo)

“If you want it to link against other pods, it’s tricky (but doable)” By that you mean if we want to have other Pods as dependencies?

Yep

Not in this case. I had to do that with firestore. It is tricky, especially with interop generation

Ah we haven't had to go that far. We just needed to be able to dynamically link custom SQLite for internal symbols

Luckily for us, the SDK is intentionally written to have no dependencies, so that won’t be an issue. Everything should be OK until an end client adds another Pod from kotlin

What do you mean?

you try to deploy kotlin multiplatform ios framework to cocoapods? but kotlin/native have limit in one kotlin framework in one project...so with your pod developer can't use other mpp library like their own busines logic?

You could deploy twice: once as a regular mpp artifact for those that already have a mpp setup and again as a pod for those who don't

“You mean you want mpp libraries that it depends on to show up in the final framework header?” Yeah, I was thinking you could pull in a bunch of dependencies in kotlin, then make one bigger framework. Like if vendor A and vendor B both publish KMP pods, you could instead make your own framework build referencing the kotlin/ios dependencies, and output one framework. However, need a way to tell the compiler that we want everything from those dependencies in the output.

the "Exporting dependencies in frameworks" section in that link is that

also you can use

transitiveExport = true

for export all to header

Ah, yeah. That’s what I was thinking about.

Ah nice. Yeah anyway, there are options built into the mpp plug-in for this :)

The only thing you might want to do is name the dependency prefix

if you use

export

or transitive export - classes not prefixed

Ah. Interesting

Good luck!