Two plugins depend on different versions of the same dependency

[Plamen5kov]

Did you verify this is a real problem by searching the NativeScript Forum and the other open issues in this repo?

Yes

Tell us about the problem

When a native-plugin "A" is added that depends on a specific version of native-dependency... "C". And another native plugin "B" depends on a different version of the native-dependency "C" cli neads to call ./gradlew clean before running build.

Which platform(s) does your issue occur on?

iOS/Android/Both
Android

Please provide the following version numbers that your issue occurs with:

• CLI: 3.4.0 + next
• Cross-platform modules: not relevant
• Runtime(s): 3.4.0 + next
• Plugin(s):

• plugin "A"(geolocation) - depends on native-dependency "C" (googlePlayServices version X)
• plugin "B"(firebase) - depends on native-dependency "C" (googlePlayServices version Y)

Please tell us how to recreate the issue in as much detail as possible.

• add geolocation plugin
• tns run android
• add firebase plugin
• tns run build (runtime fail, when you try to use geolocation functionality)

[petekanev]

@Plamen5kov how would CLI know what a plugin's dependencies are? I think this resolution is best left to the android runtime build script to handle.

[Plamen5kov]

@Pip3r4o the CLI would know that when someone does tns plugin add native-plugin-name it would have to do gradlew clean before building.

[chrillewoodz]

Any status on this?