Are there any idiocsyncracies to the cocoapods support - I've set it up as instructed but attempting to sync the project fails with <cocopod name> module not found... oddly all except one of the pods which does succeed.

Hello, there was a similar report recently, but I was unable to reproduce it. Could you please share problematic pods list?

My

cocoapods

section:

cocoapods {
        // Configure fields required by CocoaPods.
        summary = "Some description for a Kotlin/Native module"
        homepage = "Link to a Kotlin/Native module homepage"

        // You can change the name of the produced framework.
        // By default, it is the name of the Gradle project.
        frameworkName = "hydrant_art"
        ios.deploymentTarget = "14.0"

        pod("GoogleMaps")
        pod("Filament", "~> 1.9.2")
        pod("Firebase/Analytics")
        pod("Firebase/Firestore")
        pod("Firebase/Storage")
        pod("Firebase/Database")
        pod("Firebase/RemoteConfig")
    }

I remember something familiar about the

Firebase/

ones, there was a problem solvable with quite a different naming. I just tried locally, and getting rid of all those slashes made things work.

ios.deploymentTarget = "14.0"
        pod("GoogleMaps")
        //pod("Filament", "~> 1.9.2")
        pod("FirebaseAnalytics")
        pod("FirebaseFirestore")
        pod("FirebaseStorage")
        pod("FirebaseDatabase")
        pod("FirebaseRemoteConfig")

For the

Filament

, I found this thread, and everything looks really less promising. Maybe you could try pinging library maintainers somewhere like https://github.com/google/filament/issues/1197 or https://github.com/google/filament/issues/139, but at the moment this binding most probably just won’t work.

@Artyom Degtyarev [JB] Thanks very much for this information.

I totally agree. Those slashes issue us about subspecs, I’m not an expert but it is about some pods have two different versions - as a subspec and as a single pod. The second variant is what we used here now. Interestingly, I’ve just found this issue - https://youtrack.jetbrains.com/issue/KT-32750 stating the problem was fixed already. Better ask @Yaroslav Chernyshev [JB] to take a look here.

Hey @darkmoon_uk did you manage to resolve this issue? I'm having a similar problem,

pod install

works fine without any warnings but gradle sync fails with:

> Task :background-sdk:cinteropLocalzDriverSDKIos FAILED
Exception in thread "main" java.lang.Error: /var/folders/y1/f44ld52d3sl2scm9p_mdwkbc0000gn/T/tmp2184417698632498043.m:1:9: fatal error: module 'LocalzDriverSDK' not found
	at org.jetbrains.kotlin.native.interop.indexer.UtilsKt.ensureNoCompileErrors(Utils.kt:152)
	at org.jetbrains.kotlin.native.interop.indexer.ModuleSupportKt.getModulesASTFiles(ModuleSupport.kt:67)
	at org.jetbrains.kotlin.native.interop.indexer.ModuleSupportKt.getModulesInfo(ModuleSupport.kt:13)
	at org.jetbrains.kotlin.native.interop.gen.jvm.MainKt.buildNativeLibrary(main.kt:430)

In my Podfile I have

source '<https://github.com/localz/Spotz-iOS-Specs.git>'
...
use_frameworks!
...
pod 'LocalzDriverSDK', '1.7.2'

however, when I change it to (I have access to SDK source)

pod 'LocalzDriverSDK', :path => '../../ios/localz-driver-sdk-ios'

it all works fine

@Aleksey Chugaev Custom spec repos are supported in 1.4.20-M1. Please try to add

specRepos {
    url("<https://github.com/localz/Spotz-iOS-Specs.git>")
}

into

cocoapods

block where

pod("LocalzDriverSDK")

declared

thanks, will give it a try