Bug 37220 - MapboxSDK component has two conflicting package dependencies for Square.OkHttp
Summary: MapboxSDK component has two conflicting package dependencies for Square.OkHttp
Alias: None
Product: Components
Classification: Xamarin
Component: Xamarin Components ()
Version: N/A
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jon Dick
Depends on:
Reported: 2015-12-22 04:44 UTC by bobme981
Modified: 2016-01-12 15:39 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description bobme981 2015-12-22 04:44:04 UTC
From ...\Components\mapboxsdk-2.1.2\component\Manifest.xml:

    <package id="Square.OkHttp" version="2.5.0" framework="android" />
    <package id="Square.OkHttp" version="" framework="android" />
    <package id="Xamarin.Android.Support.Design" version="" framework="android" />

Notice there are two entries Square.OkHttp. Also, the second entry refers to a version that does not exist.

(See https://www.nuget.org/packages/Square.OkHttp)

When the component is added to a project, Xamarin Studio shows a red "X" icon next to it and complains that it has a dependency on a package that is not referenced by the project. However, it is impossible to create such a reference, both because the required version does not exist on NuGet, and because the project already contains a reference to a different version of the same package.

Presumably the second entry just needs to be deleted.

This kind of obvious error in a supposedly major release of the component (v3.0.0) is pretty ridiculous.
Comment 1 Jon Dick 2016-01-12 15:39:02 UTC
This will be fixed in release of the component which is pending review currently.