-
Notifications
You must be signed in to change notification settings - Fork 1.4k
support-v4 dependency fetches alpha version #480
Comments
To be fair, I do think this is something either gradle or the android are to blame. Their repository should handle it not leaking an alpha version into dependency management unless specified explicitly. |
+1 |
Same bug here. $ cordova build android
I had to to downgrade diagnostic plugin to make it work which is not satisfactory. |
Solved this build issue for me. You can give it a try. Put it to the bottom of platforms/android/build.gradle |
@macdonst This is the same base issue as the conflict between push and googleplus. |
@fredgalvao yeah, I spent the afternoon on this with the push plugin and could not get the magic incantation. I need to pull in some more folks on this. |
@macdonst You mean you're trying to see why gradle is picking alpha versions? For the issue at hand, I don't see why not just change from: Bold open versioning is always dangerous, even if gradle wasn't spitting alpha versions we could get a major bump with breakages. |
@fredgalvao in general I'm trying to get plugins that specify |
+1 For people just looking to have a succesful build while solving in a clever way, I made it by making a change in: |
@macdonst I've been encountering the same problem with 3rd party plugins - making local changes within However, I think I've found a solution based on this SO answer which uses an extra bit of Gradle config to override any existing versions specified. |
dpa99c, that did the trick for me, thanks. |
@dpa99c You saved my day bro ! Thanks a lot... |
@dpa99c Thank you, you saved my night :) Perhaps you should put a link to that repo in dpa99c/cordova-diagnostic-plugin? EDIT: I see you already did :] https://github.com/dpa99c/cordova-diagnostic-plugin#gradle-version-collisions |
Any update about this? Without an external plugin or overriding |
I'd also like plugin authors in general to use a direct/explicit approach to this issue, instead of us having to rely on a plugin to solve conflicts on specific packages. There aren't that many possible scenarios, and so I think it's worth the little effort for us to keep things stable (by simply not including alpha versions, at the very least). |
thanks @dpa99c, you save my project! |
Thanks @dpa99c, but one more question: I also use To fix this, i installed the plugins But i get an error:
I think it's because i don't include
If i include Does anybody have an idea what to do in this case? You can't use the facebook plugin without ID and name of your app. |
thanks,, you save my day |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This thread has been automatically locked. |
Expected Behaviour
Plugin to coexist with other plugins that depend on any android-support module and not fetch unstable versions of said dependencies.
Actual Behaviour
jeduan's facebook4 plugin is broken as we speak for anyone also using this or any other plugin that uses too-loose dependency requirements like
compile 'com.android.support:support-v4:+'
. Furthermore, risking using an unstable and unreleased version of a library is an anti-feature.Specing at least a major version is recommended.
Reproduce Scenario (including but not limited to)
Steps to Reproduce
jeduan/cordova-plugin-facebook4#507 provides them (just installing both plugins should sufice).
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Not applicable
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Not applicable
Cordova CLI version and cordova platform version
Not applicable
Plugin version
Since 5.0.0, it seems:
Sample Code that illustrates the problem
Not applicable
Logs taken while reproducing problem
The text was updated successfully, but these errors were encountered: