title: Android - Gradle sync failed: org/jetbrains/kotlin/kapt/idea/KaptGradleModelorg/jetbrains/kotlin/kapt/idea/KaptGradleModel
body: <p>Yesterday, without any reason, my Android Studio starts to show the following message:</p>
  
  <pre><code>Gradle sync failed: org/jetbrains/kotlin/kapt/idea/KaptGradleModelorg/jetbrains/kotlin/kapt/idea/KaptGradleModel
  Consult IDE log for more details (Help | Show Log) (2 s 227 ms)
  </code></pre>
  
  <p>But I not even using Kotlin! Those are my gradle files:</p>
  
  <p>// Top-level build file where you can add configuration options common to </p>
  
  <pre><code>all sub-projects/modules.
  
  buildscript {
  
      repositories {
          google()
          jcenter()
      }
      dependencies {
          classpath 'com.android.tools.build:gradle:3.2.1'
          // Firebase import
          classpath 'com.google.gms:google-services:4.2.0'
          // NOTE: Do not place your application dependencies here; they belong
          // in the individual module build.gradle files
  
          // Stupid kotlin build-in plugin
      }
  }
  
  allprojects {
      repositories {
          google()
          jcenter()
      }
  }
  
  task clean(type: Delete) {
      delete rootProject.buildDir
  }
  
  
  apply plugin: 'com.android.application'
  
  repositories {
      jcenter()
  }
  
  android {
      compileSdkVersion 28
      testOptions  {
          unitTests {
              includeAndroidResources = true
              returnDefaultValues = true
          }
      }
      defaultConfig {
          applicationId "com.example.olegario.escamboapp"
          minSdkVersion 21
          targetSdkVersion 28
          versionCode 1
          versionName "1.0"
          testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
      }
      buildTypes {
          release {
              minifyEnabled false
              proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
          }
      }
  }
  
  dependencies {
      implementation fileTree(dir: 'libs', include: ['*.jar'])
      implementation 'com.android.support:appcompat-v7:28.0.0'
      implementation 'com.android.support.constraint:constraint-layout:1.1.3'
      implementation 'com.android.support:design:28.0.0'
      implementation 'com.android.support:support-v4:28.0.0'
      testImplementation 'junit:junit:4.12'
      androidTestImplementation 'com.android.support.test:runner:1.0.2'
      androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
  
      // Scroll view
      implementation 'com.android.support.constraint:constraint-layout:1.0.2'
  
      // Firebase
      implementation 'com.google.firebase:firebase-core:16.0.5'
      // Firebase database
      implementation 'com.google.firebase:firebase-database:16.0.6'
      // Firebase storage
      implementation 'com.google.firebase:firebase-storage:16.0.1'
      // Firebase authentication
      implementation 'com.google.firebase:firebase-auth:16.0.5'
  
      // Mask
      implementation 'com.vicmikhailau:MaskedEditText:2.0.4'
  
      // test
      testImplementation 'junit:junit:4.12'
      testImplementation 'androidx.test:core:1.0.0'
      testImplementation 'org.mockito:mockito-core:1.10.19'
      testImplementation 'org.robolectric:robolectric:4.2'
      androidTestImplementation 'org.mockito:mockito-android:+'
      androidTestImplementation 'com.android.support:support-annotations:24.0.0'
      androidTestImplementation 'com.android.support.test:runner:0.5'
      androidTestImplementation 'com.android.support.test:rules:0.5'
      androidTestImplementation 'com.android.support.test.espresso:espresso-core:2.2.2'
      androidTestImplementation 'com.android.support.test.espresso:espresso-contrib:3.0.2'
  
      // Framework
      implementation project(':capuccino')
  
  }
  apply plugin: 'com.google.gms.google-services'
  </code></pre>
  
  <p>Why this is happening? I updated my Android Studio yesterday too, to the version 3.4, but this error started to appear after hours of the update, so I'm assuming that the update has nothing to do with the error.</p>