question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Projects using the no-arg module fail to build in Kotlin 1.6.20

See original GitHub issue

Trying to upgrade my project to 1.6.20 causes the iOS (but not Android) executable to fail. It complains

> Task :mobilemanegesharedmodule:linkDebugFrameworkIos FAILED
e: The symbol of unexpected type encountered during IR deserialization: IrSimpleFunctionPublicSymbolImpl, com.russhwolf.settings/Settings|-62081702699614493[0]. IrClassifierSymbol is expected.

This could happen if there are two libraries, where one library was compiled against the different version of the other library than the one currently used in the project. Please check that the project configuration is correct and has consistent versions of dependencies.

and then

+--- com.russhwolf:multiplatform-settings-no-arg (com.russhwolf:multiplatform-settings-no-arg-iosx64): 0.8.1
|    ^^^ This module contains symbol com.russhwolf.settings/Settings|-62081702699614493[0] that is the cause of the conflict.
|    +--- com.russhwolf:multiplatform-settings (com.russhwolf:multiplatform-settings-iosx64): 0.8.1
|    |    ^^^ This module contains symbol com.russhwolf.settings/Settings|-62081702699614493[0] that is the cause of the conflict.

Seems a little odd since I see you’ve already allowed for HMPP it seems. Perhaps it’s Kermit causing the trouble?

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:3
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

5reactions
russhwolfcommented, Apr 11, 2022

I’ve been able to isolate this to an issue in Kotlin 1.6.20 and reported it on Youtrack. You can follow it here: https://youtrack.jetbrains.com/issue/KT-51927

2reactions
russhwolfcommented, Apr 12, 2022

I’ve confirmed that you can work around the issue while still using the current published version of the library by disabling compiler optimizations as recommended in the YouTrack ticket above. Add something like this to your gradle file:

kotlin {
    targets.withType<org.jetbrains.kotlin.gradle.plugin.mpp.KotlinNativeTarget> {
        binaries.all {
            freeCompilerArgs += "-Xlazy-ir-for-caches=disable"
        }
    }
}
Read more comments on GitHub >

github_iconTop Results From Across the Web

Kotlin version conflict when using Kotlin Gradle plugins in pre ...
But when I now try to run the build, it fails (I use -Werror ) with. w: Runtime JAR files in the classpath...
Read more >
What's new in Kotlin 1.6.20
If your project consists of lots of small modules and has a build parallelized by Gradle, adding another layer of parallelization may hurt ......
Read more >
Kotlin noArg plugin not recognised by IntelliJ - Stack Overflow
With the build.gradle.kts below my application compiles OK but IntellJ underlines my Entity with error Class 'User' should have [public, ...
Read more >
kotlin/ChangeLog-1.6.X.md at master · JetBrains/kotlin - GitHub
lang.ClassNotFoundException' exception. KTIJ-20929 MPP Debugger: in a project with single JVM target evaluation of expect function fails with 'NoSuchMethodError ...
Read more >
Compose to Kotlin Compatibility Map - Android Developers
Declaring dependencies. To add a dependency on the Compose Compiler, you must add the Google Maven repository to your project.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found