Guava -jre dependency is pulling the guava-android.jar into the classpath

We have a dependency constraint enforcing the usage of guava-30.1.1-jre, however gradle seems to be resolving to the guava-30.1.1-android.jar instead. Adding a resolution strategy doesn’t seem to make any difference.

This is causing compilation errors as the android version is missing some of the classes!

You did not provide any detail about your build scripts and did not even provide a build --scan, so there will hardly anyone be able to guess what messes up your dependencies.