Hey... looking for some support. I have two iOS pr...

# compose-ios

[Saud Khan]

Hey... looking for some support. I have two iOS projects that were recently converted to use Cocoapods for the KMP framework vs directly using the Framework. One of them that is fully built on Compose MP is working well and as expected. However, the other one is running into an issue with the multi-module resources (which both use btw)

* What went wrong:
Execution failed for task ':app:first:syncPodComposeResourcesForIos'.
> Cannot query the value of this provider because it has no value available.

Google search just ends up in old threads that tells you to disable that task, but then of course the resources are not compiled in.
Some think about the set up:
• Kotlin 2.0.21
• Compose MP: 1.7.3
• multi-module with resources in different modules
• modules are shared between app "first" and "second"
• app "second" is larger with more modules and most modules have resources and working well
• app "first" has mainly 4 modules with resources and is set up almost identically otherwise
• both app modules have resources in commonMain/composeResources also
Any one have any suggestions on what I should try?

[Dmitry Motyl]

I combine my submodules in the big one for iOS
Do you add your modules separately by cocoapods?

[Saud Khan]

Nope. They are included into the big framework which is included by Cocoapods

[Vlad]

Any luck resolving that?
After I moved my resources from the root module exported as cocoapod into ios - the resources are not copied

[Saud Khan]

Sadly I no longer have access to that project, and couldn't resolve it while I was working on it.

[Saud Khan]

I have the same issue that you saw, with the resources not being copied.

[Artem]

Hey @Vlad, were you able to solve this problem?

[Vlad]

@Artem Sorry for the late response. I am not sure if my issue is the same as in the topic. I don't use resources generated by compose from Swift or anywhere in iosApp module.
But yes, I managed to have resources in the deeper module :composeApp -> coreresources.
It is unclear when the resources are copied and when not, because of the cache. But seems like adding the

implementation(compose.components.resources)

in the :composeApp even tho the resources deeper - did the trick.
Plus my dependency on coreresources are marked as API, but I can't say for sure that is exact for that reason, coz we are still in the migration from single module project.