i’ve just upgraded to gradle 7 (using `./gradlew w...

# gradle

[William Reed]

i’ve just upgraded to gradle 7 (using ./gradlew wrapper --gradle-version 7.0.2) and my kotlin gradle scripts show many errors saying something similar to

Cannot access 'kotlin.collections.Collection' which is a supertype of 'org.gradle.api.artifacts.dsl.RepositoryHandler'. Check your module classpath for missing or conflicting dependencies

i don’t see any reason this should happen based on the gradle 7 docs. any ideas?

[Emil Kantis]

Sounds odd.. Does ./gradlew clean build --no-build-cache work?

[William Reed]

that seems to work now and so does the ‘hammer’ inside android studio. the errors still show up in the IDE with the files open though hmm

[Emil Kantis]

Invalidate cache in IntelliJ is usually a good first step 😄

[kevindmoore]

I usually have to run gradle from the command line to get any meaningful errors. I've seen that error but can't remember the solution (I've had so many lately)

[William Reed]

unfortunately the same thing after invalidating intellij cache which is weird

[William Reed]

i’ve tried changing the IDE java version to the bundled one (jdk 11), my own install of jdk 11, and my own install of jdk 8 but no changes hmm

[William Reed]

well i wound up nuking my whole install, and reinstalling, and things are working fine now

[theapache64]

@William Reed For me, deleting the cache worked

sudo rm -R ~/Library/Caches/Google/AndroidStudio2020.3

[William Reed]

i’ll try that if it happens again