zxing3.6.0 / support:appcompat-v7 error...
See original GitHub issueDescription of the problem:
I try…
-
Create New Project
-
target sdk version 28, min sdk version 19
-
compile sdk version 28
-
insert gradle dependencies : implementation ‘com.journeyapps:zxing-android-embedded:3.6.0’
-
implementation ‘com.android.support:appcompat-v7:28.0.0’ <-Error…
All com.android.support libraries must use the exact same version specification (mixing versions can lead to runtime crashes). Found versions 28.0.0, 25.3.1. Examples include com.android.support:animated-vector-drawable:28.0.0 and com.android.support:support-media-compat:25.3.1 less… (⌘F1) There are some combinations of libraries, or tools and libraries, that are incompatible, or can lead to bugs. One such incompatibility is compiling with a version of the Android support libraries that is not the latest version (or in particular, a version lower than your targetSdkVersion).
How can fix…??? T_T
android {
compileSdkVersion 28
defaultConfig {
applicationId "com.example.yoonho.jitest"
minSdkVersion 19
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(include: ['*.jar'], dir: 'libs')
implementation 'com.android.support:appcompat-v7:28.0.0' // <-Error Here!!!
implementation 'com.android.support.constraint:constraint-layout:1.1.3'
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'
implementation 'com.journeyapps:zxing-android-embedded:3.6.0'
}
Which library version are you using? E.g. 3.6.0.
**Which phone/tablet are you using, and which Android version does it run? ** galaxy s4
Does the same happen on other devices or an emulator? same happen on other emulator
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (2 by maintainers)
Top GitHub Comments
The main library is an aar file anyway, even without the
@aar
annotation. I suspect that specifying explicitly does roughly the same as this:Which basically says “use this library, but none of its dependencies”.
Hi, I think the @aar annotation implements a compiled binary, while without that annotation it drops a copy of the repository to be compiled with your project and that’s where the error appears