Just updated to Compose MP 1.6.0-beta2, and so far...

# compose-ios

[tylerwilson]

Just updated to Compose MP 1.6.0-beta2, and so far everything is working as expected. Very nicely done! Was also able to remove material2 dependency and use the newer PullToRefresh in material3 on Android and iOS.

[Joel Denke]

Oh its released now, sweet. Does resources work multi module now?

[tylerwilson]

I have not tried any resource related stuff yet.

[uli]

which dependency holds the pulltorefresh for ios?
I thought it was only in material3-android

[uli]

I checked again. and yes, it’s in the basic material3 dependency, available for cross platform.
Thanks for making me check again :-)

[Joel Denke]

Lol everything broke in Material 3 and compose foundation 😄 Not CMP fault, blaming Google.
Just some minor tweaking needed by me for resources relative paths I think, and I am up and running beta02 as well in same state as 1.5.12 release.

[uli]

I am currently fighting with a multi module project and resources. iOS does not see it’s strings. Hints i found on the internet to run cocoapods seem not to apply any more.

[uli]

I’ll try and at least nail down what exactly the issue is. It’s gonna be a challenge, because it’s a new project that never worked

[uli]

1) It seems like string resources work fine in the main app module

[uli]

2) Even changes get picked up in the iOS app on rebuild in AS

[uli]

3) Resources in a second module are not visible to the main module. (I guess that’s expected)

[uli]

4) 😞 Resources in a second module are visible to that module but access causes an exception during runtime:

kotlin.IllegalStateException: String ID=`xyz` is not found!

[Andrew Watson]

I was wondering about this as well; so it would appear that the build process still isn't merging resources for iOS?