Hello all. Does anybody know why cocoapodsext and ...

# touchlab-tools

[esdudnik]

Hello all.
Does anybody know why cocoapodsext and cocoapods gradle plugin doesn’t work on Xcode 11.5? Made everything as described here
https://github.com/touchlab/KaMPKit/blob/master/docs/IOS_PROJ_INTEGRATION.md
Just replaced cocoapods with cocoapodsext (as here https://github.com/touchlab/KaMPKit/blob/master/shared/build.gradle.kts)
gradle task(“podspec”) works, pods generated, after adding in Podfile, dependency added(“pod install” install my commonCode), in Xcode in “Development Pods” my commonCode framework exist, but building project in Xcode show error

ld: framework not found commonCode
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Xcode version 11.5, Android studio 4.1, Gradle plugin version “4.1.0-alpha10", Kotlin “1.3.72”.
I tried both

id("co.touchlab.native.cocoapods")
id("org.jetbrains.kotlin.native.cocoapods")

but none of them works with Xcode 11.5

[russhwolf]

You may need to update your cocoapods version. That helped for this issue that sounds similar https://kotlinlang.slack.com/archives/CTJB58X7X/p1590137654078200

[esdudnik]

Hi Russell. Thanks for your reply. I am using cocoapods 1.9.3 version. The problem occurs after updating Xcode to 11.5. On previous version of Xcode(actually don’t remember what was it before update) touchlab and jetbrains cocoapods plugin both worked.

[russhwolf]

I can get a vanilla KaMPKit clone building in 11.5, so I don’t think it’s an Xcode incompatibility. Not quite sure what’s going wrong.

[esdudnik]

Hi Russell. Your last message push me to correct directions. I compare with KaMPKit repo and found that I am missing framework path from Target - > Build Settings -> Search Path. So I added it and it works now. I am actually thinking that cocoapods plugin adds this path when installing development pods. Maybe I deleted this path when I migrate from “ios” target and packForXcode gradle task. Anyway it works now, so big thank for your help)

[russhwolf]

There’s a couple different common ways xcode can be configured, so easy to get mixed up there. Good to know you have it working now.