I'm running through the <getting-started for Kotli...

# multiplatform

[dallas]

I'm running through the getting-started for Kotlin Multiplatform with Compose, have built my project using the linked Wizard, downloaded, and trying to run from Android Studio but getting the following...

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

the run configuration was already there for me -- didn't set one up myself... and I did open Xcode before running. Android (composeApp) runs fine

Any ideas?

[Pablichjenkov]

Did you set "search framework path" and "other linker flags" in your Xcode build settings?

[dallas]

I didn't change anything in Xcode, no

[dallas]

I don't see that in the docs, but I found the setting for the first one you mentioned and it has this:

[Pablichjenkov]

That one looks good

[dallas]

image.png

[dallas]

This was all set up by the Wizard from the thing I linked. A friend of mine cloned my repo and ran this from Xcode just fine 😐

[Pablichjenkov]

I believe that should work.

[dallas]

Same Xcode version. I'm on Sonoma he's on Ventura

[Pablichjenkov]

Ahh well, in such a case perhaps it is something else.
Perhaps something changed and you don't need to specify where to search for the xcframework anymore.

[Pablichjenkov]

Are you able to run it from xCode?

[dallas]

Nope, basically same error

[dallas]

image.png

[Pablichjenkov]

Humm, it seems like due to some problem it is not able to compile it. There is no other error before?

[dallas]

One sec I'll post the whole gist

[Pablichjenkov]

Are you able to see a /build directory inside your module

[dallas]

Whole output from runnign iosApp in AS: https://gist.github.com/dallasgutauckis/01db4832828e01e35c597735904d1a0d

[Pablichjenkov]

Sometimes Xcode complains because I have not setup my provision profile

[dallas]

Inside which module, sorry

[dallas]

composeApp?

[dallas]

or iosApp?

[dallas]

I have composeApp/build

[dallas]

inside there, xcode-frameworks

[dallas]

Is the provisioning profile just for installing on real devices?

[Pablichjenkov]

Can you try a different device version. I believe there was some issues with iPhone 17

[Pablichjenkov]

Try a simulator that runs Xcode 16

[dallas]

Well my buddy is using the same version of Xcode (15.0.1)

[dallas]

I'm downloading iOS 16.4 sim now

[Pablichjenkov]

Xcode 15 is fine I think is the latest iOS version the one having some issues.

[dallas]

Same issue on 16.4

[Pablichjenkov]

In the logs you posted I don't see anything relevant. I think it shows your java home empty but not sure if that is relevant.

[dallas]

Yeah the only relevant thing I saw was the error at the bottom about composeApp

[dallas]

And of course again, Android runs fine 😕

[Pablichjenkov]

Same issue on 16.4

Ouch, well, wait to see if someone from JB takes a look into it

[dallas]

I think I've figured it out -- at least what the problem is but not the root of the problem which I assume is a config problem somewhere in the wizard. I have a case-sensitive filesystem for my projects on my mac and I think somewhere the configuration is ComposeApp vs. composeApp

[dallas]

This, I think, is a bug in the wizard

[dallas]

Changing to a case-insensitive filesystem allowed me to run the iOS app without issue.

[Pablichjenkov]

Humm, interesting. good finding. Usually the framework name is defined using:

iosTarget.binaries {
            framework {
                baseName = "MyFrameworkNameKt"
                isStatic = true
            }
        }

Hopefully you find where is the misspell because I guess someone else will run into the same problem if clone your code.