Has anyone experienced an issue with a `Missing Resource Exception` It seems as though the `compose-...

# compose-ios

[Dmitriy Tarasevich]

Has anyone experienced an issue with a Missing Resource Exception It seems as though the compose-resources directory is one level deeper in the app package than it should be. If I were to manually move that to where KM is looking for it works.

There is a similar ticket to https://youtrack.jetbrains.com/issue/KT-66790

[Konstantin Tskhovrebov]

There is no way to use resources with XCFramework artefact yet. The only way is to build an application

[Dmitriy Tarasevich]

can you elaborate on the difference between XCFramework vs "build an application" ?

[Konstantin Tskhovrebov]

build an app = link framework + provide resources to the Xcode project

[Dmitriy Tarasevich]

which is all done through the embedAndSignAppleFrameworkForXcode task correct?

[Dmitriy Tarasevich]

I think I understand where we are having an issue now... We have multiple iOS modules which all rely on the shared KM code. So we run the embd task but then take the framework and wrap it in a framework so that all the modules can reference it and not have to each run the embed task themselves

[Dmitriy Tarasevich]

Do you see a better way to potentially set this up?

[Konstantin Tskhovrebov]

https://youtrack.jetbrains.com/issue/KT-66790#focus=Comments-27-9864191.0-0

[Konstantin Tskhovrebov]

The correct way is to build your application locally (not XCFramework)

[Dmitriy Tarasevich]

is that the same as running embedAndSignAppleFrameworkForXcode in the scripts?

[Konstantin Tskhovrebov]

yes

[Benoit Billington]

When using cocoapods the solution is to add

spec.resources = ['*']

[Kapil Yadav]

Where to use this ? @Benoit Billington

[Marcel]

If we don't have a monorepo (KMP in a different repo than iOS) what could we do here?
Could we perhaps use something like a git submodule and fetch the resources in that way?