hwadraw.blogg.se - Download ksp 1.3 for free

Alternatively, both the kotlin and tools:gradle versions can be downgraded to compatible version that match metadata (although Android Studio will warn for that not matching the IDE Kotlin version) How to Prevent this from happening Again? NOTE: your dependencies may need to be updated if their :gradle version is too old.

ensure the android/gradle/gradle-wrapper.properies has the correct distributionUrl (currently distributionUrl=https\:///distributions/).(I don't know why it suggests this older version) 7.3.1 is currently the latest and is meta data 1.7.1, so it will match the Kotlin version of 1.7.20 (which is also metadata 1.7.1) What else could be wrong?ĭue to caching, gradle may be using an older dependency before you updated.

Now you don't have any warnings, but the version suggested is 7.1.3 which is not the latest.

The user updates the android build tools gradle plugin per the warning.

The user updates the Kotlin version of the plugin to match the IDE version per the warning.

The binary version is the what is downloaded (or previously compiled)Įxt.kotlin_version = '1.5.20' // <= expected version is 1.5.1Ĭlasspath ':gradle:7.3.1' // downloads 1.7.1 MetadataĬlasspath ":kotlin-gradle-plugin:$kotlin_version" // <= 1.5.20 used here The expected version is the Kotlin for kotlin-gradle-plugin

Although this question has been answered, I think it's worth explaining what is happeningįor the example: The binary version of its metadata is 1.7.1, expected version is 1.5.1.