Compose-Multiplatform Resources for ios doesn't work with Moko-Resources about compose-multiplatform

[terrakok]

The restrictions were deleted in the master

[ExNDY]

@terrakok Hi, i'm write you about this question.

[pjBooms]

Duplicate to #4499.
@AlexeyTsvetkov please remind the context of the issue.

[jbruchanov]

I'd add to this as well..
Please don't make the resources breaking other implementations.
I've done my own implementation as well to have all the useful features like locale/display qualifiers/plurals etc, and it'd be just the best if the resources became a simple opt-in extension and not something what is breaking other libs, or something what is forcibly disabling other libs from the usage...

[terrakok]

The compose gradle plugin does a resource packaging for iOS targets as part of its final artifacts build. The plugin has a logic how to get target resources and to copy them to a resource's bundle.
Sorry, we don't provide a public API here and don't give guaranies for other plugins (like a bundle name, an inner structure or tasks names). So, if you create 3d party plugin for resources you are suppose to implement its own resource bundle packaging logic and to copy the custom bundle to the final application.

We plan to delete the restrictions for other plugins on our side but it doesn't mean we supported them. It is responsibility the plugins authors.

P.S.: there is a drawback, the compose gradle plugin packs all target's resources to the compose resources bundle (not only from composeResources directory). We may change it in a future. No guaranties here. That is why you are suppose to implement own bundle here.