You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Upgrade kotlin-metadata-jvm tool in JNIgen to support version 2.4.0 and newer #3597
Flutter 3.47 has bumped the default recommended Kotlin version (including in project templates) to 2.4.0.
It makes sense to upgrade kotlin-metadata-jvm so that the minimum supported language version is at least 2.4.0.
Flutter updates seem to move faster than JNIgen updates for some reason. Perhaps patches for upgrading kotlin-metadata-jvm could be released more often, or at least before a new stable version of Flutter approaches release window?
Also, Flutter shows the following warning when building an application (for JNIgen generation) with a language version lower than 2.4.0:
Warning: Flutter support for your project's Kotlin version (2.3.0) will soon be dropped. Please upgrade your Kotlin version to a version of at least 2.3.20 soon.
Alternatively, use the flag "--android-skip-build-dependency-validation" to bypass this check.
Potential fix: Your project's KGP version is typically defined in the plugins block of the `settings.gradle` file, by a plugin with the id of org.jetbrains.kotlin.android.
If you don't see a plugins block, your project was likely created with an older template version, in which case it is most likely defined in the top-level build.gradle file by the ext.kotlin_version property.
This is fixed at HEAD, so you'll see the update when I publish the new version of jnigen (some time this week). But I did find a couple more places in the monorepo that haven't been bumped yet, in the jni_flutter example and test.
Activity
liamappelbe commentedon Aug 30, 2026
This is fixed at HEAD, so you'll see the update when I publish the new version of jnigen (some time this week). But I did find a couple more places in the monorepo that haven't been bumped yet, in the jni_flutter example and test.