-
-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
android.support library version conflicts #212
Comments
You may have another plugin installed in your project which specifies, for example, console output for build using `cordova.plugins.diagnostic@3.6.4`
i.e. console output for build using `cordova.plugins.diagnostic@3.6.5`
i.e. |
dpa99c , good day ! Could you suggest please how to fix this ? I am not professional android developer, I am using Ionic3. |
@klochko7 The most likely cause is a Gradle version conflict with another plugin in your project. You need to go through each |
The problem is with https://github.com/phonegap/phonegap-plugin-barcodescanner/blob/master/src/android/barcodescanner.gradle#L15 It works find with cordova 7.0.1 but not with cordova 6.5.0 |
@frankkoenigstein Seems there's an issue opened against that plugin which covers it: phonegap/phonegap-plugin-barcodescanner#480. But I will close the issue because this plugin can do nothing about the Gradle versioning in other plugins. |
In my progect I found only one place with it in de.appplant.cordova.plugin.local-notification ...
I change to
But now I see .. FAILURE: Build failed with an exception.
BUILD FAILED Total time: 25.35 secs
Error: cmd: Command failed with exit code 1 Error output:
|
I did ..
and unfortunately see ... :processArmv7DebugManifest FAILED BUILD FAILED Total time: 14.779 secs FAILURE: Build failed with an exception.
Error: cmd: Command failed with exit code 1 Error output: FAILURE: Build failed with an exception.
|
@klochko7 that error implies something (a plugin) is still pulling in |
dpa99c, BUILD SUCCESSFUL, but I need unfortunately to delete .. сordova-plugin-crosswalk-webview ... this plugin helps my app run well on Android < 5 .. Could I fix this ? |
@klochko7 From what I can see, the crosswalk plugin itself doesn't specify any versions of these libraries, so it's likely that they are being specified by the crosswalk engine itself which is itself being pulled in by Gradle via the plugin. To that, there's not much of an easy solution. You can try going through the .gradle files in As @fredgalvao rightly said, the fault really lies with Gradle/Android for allowing alpha versions to leak out without them being specifically requested. |
dpa99c, ok I will try .. |
Who ever put this note into plugin readme.md.... I love you If your build fails with an error such as this:
Then it's likely that the build failure is due to a collision caused by another plugin requesting a different version of the Android Support Library (see #212, #211, #205, etc.). |
configurations.all { |
@yaminijain cordova-android-support-gradle-release does exactly this in order to override the versions specified by other plugins (e.g. this one) in order to resolve conflicts:
This allows the problem to be solved without need for manual modification of the |
Diagnostic plugin references two libraries:
After updating this plugin the android compile exits with the following error:
Looks like there is a alpha release
com.android.support:support-v4:26.0.0-alpha1
which should not be used. Please update yourplugin.xml
to references an explicite version of android support libraries:The text was updated successfully, but these errors were encountered: