Hey again, Im having problem with cocoapods refere...

# multiplatform

[Ahmet Özcan]

Hey again,
Im having problem with cocoapods referenced from kmm module
i added PubNub pod to one of my kmm modules but then i tried to build ios iget this error

Undefined symbol: _OBJC_CLASS_$_PubNub

Can you help me about that pls
ty.

[kpgalligan]

That error says the pubnub binary can't be found. Adding the pod to Gradle only tells cinterop about the headers. It should also add the dependency to your podspec. Are you using cocoapods for integrating into xcode?

[kpgalligan]

I gave a talk about the difference between cinterop and linking (part of the talk anyway) https://www.droidcon.com/2022/08/01/sdk-design-and-publishing-for-kotlin-multiplatform-mobile-2/

[Ahmet Özcan]

You mean i also need to add cocopod dependency to iosApp PodFile ?

[Ahmet Özcan]

I ll look into it thank you very much

[kpgalligan]

The podspec file that Kotlin generates should include a reference to whatever pod dependencies you have in the Gradle config. which should pull that into your overall cocoapods build and the Pods directory. Hard to say without looking at the whole thing. You can also add it to the Podfile directly just in case.

[Ahmet Özcan]

its included in the podspec file
but its only works if i add the pod in the pod file manually

[kpgalligan]

Odd. Looks like more of a cocoapods specific thing than kotlin. That should be able to access the dependency. I personally prefer to be specific with iOS dependencies in the 'Podfile' anyway. The iOS devs (if there are iOS devs) get to control versions and there aren't any surprise inclusions. Depends on the situation, though

[Ahmet Özcan]

there are some wierd stuffs going on there for example there is a method on the cinterop with 3 parameters but its actually 2 in the pubnub objectivec sdk

[Ahmet Özcan]

and using this method from iosMain breaks the compilation

[Ahmet Özcan]

maybe its better to implement that on ios and send to kmm over di with an intrface 🙂

[Ahmet Özcan]

thank you for your time Kevin and thank you to your team also 🙂