Unable to link downstream project consuming Kotlin/Native-built runtime
See original GitHub issue> Task :molecule-runtime:linkDebugTestIosSimulatorArm64 FAILED
e: Compilation failed: Failed to compute the detailed error message. See the root cause exception.
Shortly: The required symbol androidx.compose.runtime/remember|-4100818973694024771[0] is missing in the module or module dependencies. This could happen if the required dependency is missing in the project. Or if there is a dependency that has a different version (without the required symbol) in the project than the version (with the required symbol) that the module was initially compiled with.
I have kotlin.native.cacheKind=none
set in the project’s gradle.properties
but it still does not compile.
Repro on this branch https://github.com/cashapp/molecule/tree/jw/link-thing/2022-09-21 running ./gradlew -p molecule :m-r:check
.
Issue Analytics
- State:
- Created a year ago
- Reactions:9
- Comments:18 (2 by maintainers)
Top Results From Across the Web
Downstream pipelines - GitLab Docs
The user triggering the upstream pipeline must be able to start pipelines in the downstream project, otherwise the downstream pipeline fails to start....
Read more >Need to fail upstream project if downstream ... - Stack Overflow
I want upstream project to fail if downstream project fails. I am using Trigger Parameterized build on other projects option to trigger ...
Read more >How to Create Upstream and Downstream Jobs in Jenkins
Your browser can't play this video. Learn more.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@saket Yeah, for now Composable functions for native can be only internal or private. We will fix it in the future.
@saket I had the same error in my case when using molecule. Its was caused due that composable functions couldn’t be public in native (at least this is what I’ve read). I fixed it changing them to internal (an in my case only expose the flow created by the molecule launch)