A modern programming language that makes developers happier.

kotlinlang

hi
how to set bundle id for iOS framework ,
I'm trying to silence this warning

```w: Cannot infer a bundle ID from packages of source files and exported dependencies, use the bundle name instead: &lt;&gt;. Please specify the bundle ID explicitly using the -Xbinary=bundleId=&lt;id&gt; compiler flag.```

Hi Ahmed, how did you set up your KMP project?

something like this, using cocoapods

```kotlin {
    androidTarget {
        publishLibraryVariants("release")
    }
    iosX64()
    iosArm64()
    iosSimulatorArm64()

    cocoapods {
        // Required properties
        // Specify the required Pod version here. Otherwise, the Gradle project version is used.
        version = "0.0.1"
        ios.deploymentTarget = "12.0"
        name = "myFramework"
        framework {
            baseName = "myFramework"
            isStatic = false
            transitiveExport = false
            embedBitcode(org.jetbrains.kotlin.gradle.plugin.mpp.BitcodeEmbeddingMode.DISABLE)
        }
    }
}```

No, I mean - did you use KMM plugin, or <http://kmp.jetbrains.com|kmp.jetbrains.com>'s wizards, or did you set things up yourself?

I'm going to try to create a project the same way and see if I can reproduce the error :slightly_smiling_face:

Ok, did you create it with the most recent plugin (0.8.1)? It was released early Nov...

i did create it 1 year back , not sure what was the version

i'll try to use the new one too , and see if warning is shown

it's not blocking anything just wondering why it's needed and how to resolve

I just created a project, I'm not seeing that warning. If you want to manually set it, I think you can use Xcode (General -&gt; Identity -&gt; Bundle Identifier).

But I think the best is to recreate the project, then you have all the latest developments and setup.

I've seen this same error compiling <https://github.com/jeffdgr8/kotbase|my library> recently, seems like it started after a recent Kotlin version update. I haven't had a chance to look into it, as it hasn't caused any issue other than the warning logs.