AppLovinMax InMobi Adapter failes the build with gradle error about "queries" keywords in Unity 2019.4

There is my base gradle template (sorry I couldn't upload a file, it stucked on uploading):

 // GENERATED BY UNITY. RE$$anonymous$$OVE THIS CO$$anonymous$$$$anonymous$$ENT TO PREVENT OVERWRITING WHEN EXPORTING AGAIN
 
 allprojects {
     buildscript {
         repositories {**ARTIFACTORYREPOSITORY**
             google()
             jcenter()
         }
 
         dependencies {
             // If you are changing the Android Gradle Plugin version, make sure it is compatible with the Gradle version preinstalled with Unity
             // See which Gradle version is preinstalled with Unity here https://docs.unity3d.com/$$anonymous$$anual/android-gradle-overview.html
             // See official Gradle and Android Gradle Plugin compatibility table here https://developer.android.com/studio/releases/gradle-plugin#updating-gradle
             // To specify a custom Gradle version in Unity, go do "Preferences > External Tools", uncheck "Gradle Installed with Unity (recommended)" and specify a path to a custom Gradle version
             classpath 'com.android.tools.build:gradle:4.1.0'
             **BUILD_SCRIPT_DEPS**
         }
     }
 
     repositories {**ARTIFACTORYREPOSITORY**
         google()
         jcenter()
         flatDir {
             dirs "${project(':unityLibrary').projectDir}/libs"
         }
     }
 }
 
 task clean(type: Delete) {
     delete rootProject.buildDir
 }
 

Spent the whole day stressing over this issue! It's night time now, I've already clocked more than 10 hours! And just as I'm about to give up, I find this post! Thank you!

Thank you king. I was having this problem with Iron Source or one of its mediation plugins (Unity or AdMob,) and don't know anything about the mess that is Gradle. This tip was much needed. Here's a direct link to the Gradle binaries for others that end up here: https://gradle.org/releases/

After much trial and error I used 5.6.4 and plugin version 3.6.4--whatever that means. The distributors of the third party libraries should be notified of this so that they can include it in their integration documentation, but who has time for that?

Lastly, I'm on 2018.4, and the build actually fails with the error "FileNotFoundException: Temp/gradleOut/build/outputs/bundle/release/gradleOut.aab does not exist" however, I was able to get around this issue by manually grabbing the file "gradleOut-release.aab" from "Temp/gradleOut/build/outputs/bundle/release/". The reason it fails is due to 2018.4 hardcoding gradleOut.aab as the filename, which is no longer what the output file is named in newer versions of Gradle, I assume.