-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error building a sample app for iOS - Module runtime-saveable has a reference to symbol androidx.compose.runtime/remember|-2215966373931868872[0] #2046
Comments
The workaround is to add |
Hello Ive this error with compose 1.2.2 , the workaround ( kotlin.native.cacheKind=none to gradle.properties) didnt not work
|
@multiport Can you please share a reproducible example of your issue on GitHub? |
Have a reproducible example here xxfast/NYTimes-KMP@860ae44 I've disable the cache on subsequent commit which seems to fix this, but would like if we can keep the cache around |
I'm getting the same issue but with a macOS target. My project is here: https://github.com/zacharee/SamloaderKotlin. It seems like it comes up as soon as |
Ran into this as well and doing a |
Currently facing the same issue while trying running the app on iOS with with the error:
It's working and run perfectly on Android, any help? |
@mustfaibra |
The core issue was fixed in Kotlin.
|
Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks. |
I'm trying to add support of Compose for iOS to the Decompose Counter sample. The app runs just fine using the task
iosDeployIPhone12ProDebug
. However./gradlew build
fails with the following error.e: Module "org.jetbrains.compose.runtime:runtime-saveable (org.jetbrains.compose.runtime:runtime-saveable-uikitx64)" has a reference to symbol androidx.compose.runtime/remember|-2215966373931868872[0]. Neither the module itself nor its dependencies contain such declaration.
Kotlin: 1.6.21
Gradle: 7.3.3
Compose: 1.2.0-alpha01-dev675
Details
The text was updated successfully, but these errors were encountered: