Support Annotation does not exist after upgrading to Android Studio 3.0

47.2k Views Asked by At

After I upgrade my project to AndroidStudio 3.0-beta1, my androidTest files stopped compiling.

A lot of packages are not found, some of them are:

error: package android.support.annotation does not exist
error: cannot find symbol class StringRes
error: cannot access AppCompatActivity
class file for android.support.v7.app.AppCompatActivity not found

I already added

androidTestCompile "com.android.support:support-annotations:25.3.1"

into build.gradle

But even with this, I have the errors of package not found. I tried running the tests from inside Android Studio and from terminal with ./gradlew connectedCheck

5

There are 5 best solutions below

4
On BEST ANSWER

I had the same problem. The issue is not that you upgraded AndroidStudio but that your target version and compile version are below 26 after updating the build tools in your SDK.

So changing

android {
    compileSdkVersion 25

    defaultConfig {
        applicationId "bla.bla"
        minSdkVersion 21
        targetSdkVersion 25
    }
}

to

android {
    compileSdkVersion 26

    defaultConfig {
        applicationId "bla.bla"
        minSdkVersion 21
        targetSdkVersion 26
    }
}

solves the issue.

1
On

Just add this to your dependencies

implementation 'com.github.bumptech.glide:glide:4.9.0'
annotationProcessor 'com.github.bumptech.glide:compiler:4.9.0'
implementation "com.android.support:support-annotations:28.0.0"
annotationProcessor 'com.android.support:support-annotations:28.0.0'

0
On

I had got similar errors and corrected it by adding.

LOCAL_STATIC_JAVA_LIBRARIES += android-support-v4
inside your Android.mk folder.

Note: This is for change in binary directly where you have to run .mk file separately. If using Android Studio, check Writing Android.mk file in Studio.
I read the previous answer and wanted to provide a different approach to correct it although its harder this way.

0
On

Try this:

import androidx.annotation.StringRes
0
On

In my case it happened after migrating to androidX . The decision merely was :

go to the *.java file(s) pointed and comment strings with packages

 //import android.???

and re-import androidX-ed ones.

Build the project again and you are done.