SyntaxFix

[android] Conflict with dependency 'com.android.support:support-annotations'. Resolved versions for app (23.1.0) and test app (23.0.1) differ

You can force the annotation library in your test using:

androidTestCompile 'com.android.support:support-annotations:23.1.0'

Something like this:

  // Force usage of support annotations in the test app, since it is internally used by the runner module.
  androidTestCompile 'com.android.support:support-annotations:23.1.0'
  androidTestCompile 'com.android.support.test:runner:0.4.1'
  androidTestCompile 'com.android.support.test:rules:0.4.1'
  androidTestCompile 'com.android.support.test.espresso:espresso-core:2.2.1'
  androidTestCompile 'com.android.support.test.espresso:espresso-intents:2.2.1'
  androidTestCompile 'com.android.support.test.espresso:espresso-web:2.2.1'

Another solution is to use this in the top level file:

configurations.all {
    resolutionStrategy.force 'com.android.support:support-annotations:23.1.0'
}

Examples related to android

• Under what circumstances can I call findViewById with an Options Menu / Action Bar item? • How to implement a simple scenario the OO way • My eclipse won't open, i download the bundle pack it keeps saying error log • getting " (1) no such column: _id10 " error • java doesn't run if structure inside of onclick listener • Cannot retrieve string(s) from preferences (settings) • strange error in my Animation Drawable • how to put image in a bundle and pass it to another activity • FragmentActivity to Fragment • A failure occurred while executing com.android.build.gradle.internal.tasks

Examples related to gradle

• Gradle - Move a folder from ABC to XYZ • A failure occurred while executing com.android.build.gradle.internal.tasks • Gradle: Could not determine java version from '11.0.2' • Android Gradle 5.0 Update:Cause: org.jetbrains.plugins.gradle.tooling.util • Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0 • Failed to resolve: com.android.support:appcompat-v7:28.0 • Failed to resolve: com.google.firebase:firebase-core:16.0.1 • com.google.android.gms:play-services-measurement-base is being requested by various other libraries • java.lang.NoClassDefFoundError:failed resolution of :Lorg/apache/http/ProtocolVersion • Error - Android resource linking failed (AAPT2 27.0.3 Daemon #0)

Examples related to android-gradle-plugin

• WARNING: API 'variant.getJavaCompile()' is obsolete and has been replaced with 'variant.getJavaCompileProvider()' • Android Material and appcompat Manifest merger failed • Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve • Failed to resolve: com.google.firebase:firebase-core:16.0.1 • com.google.android.gms:play-services-measurement-base is being requested by various other libraries • Invoke-customs are only supported starting with android 0 --min-api 26 • error: resource android:attr/fontVariationSettings not found • Exception : AAPT2 error: check logs for details • Could not resolve com.android.support:appcompat-v7:26.1.0 in Android Studio new project • Failed to resolve: com.android.support:appcompat-v7:27.+ (Dependency Error)

Examples related to build.gradle

• Android Material and appcompat Manifest merger failed • Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve • Android dependency has different version for the compile and runtime • Setting up Gradle for api 26 (Android) • What's the difference between implementation and compile in Gradle? • More than one file was found with OS independent path 'META-INF/LICENSE' • Android Studio - Failed to notify project evaluation listener error • Gradle error: Minimum supported Gradle version is 3.3. Current version is 3.2 • All com.android.support libraries must use the exact same version specification • DELETE_FAILED_INTERNAL_ERROR Error while Installing APK

Examples related to android-espresso

• Conflict with dependency 'com.android.support:support-annotations'. Resolved versions for app (23.1.0) and test app (23.0.1) differ