Bug 22026 - Component manager fails to restore a component used in multiple projects in the same solution
Summary: Component manager fails to restore a component used in multiple projects in t...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 3.4
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-08-12 01:45 UTC by softlion
Modified: 2016-12-22 19:18 UTC (History)
4 users (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 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 softlion 2014-08-12 01:45:06 UTC
In a solution which contains multiple android library projects using the same component (support v4 for example), if you update the component to its latest version on one project, then you check in in source control, then you get latest from source control on another machine, the component manager will only restore the latest version of the component, thus leaving a solution which won't compile.
Comment 1 Jatin 2014-12-18 07:14:33 UTC
I have tried this at my end and I am not able to reply this issue at my end. Below are the steps followed:

1. Created a solution with two android projects
2. Added the component Android Support v4 version in both the projects
3. Updated the the component to Android Support v4 in one of the project.
4. Build the solution.
5. The solution build successfully.

Below is the screencast for the same:

Supplement information:
Built output: https://gist.github.com/saurabh360/6588ec8771aa355f5cb6
XVS logs: https://gist.github.com/saurabh360/8d6d95c7a88f74140e01

Build information:
XVS 3.9.164
VS 2013

=== Xamarin Studio ===

Version 5.7 (build 652)
Installation UUID: 522f0c5e-80a3-4414-aec7-1f3b9c1768d1
    Microsoft .NET 4.0.30319.18408
    GTK+ 2.24.22 (MS-Windows theme)
    GTK# 2.12.26

=== Xamarin.Android ===

Version: 4.20.0 (Business Edition)
Android SDK: C:\Users\Admin\AppData\Local\Android\android-sdk
    Supported Android versions:
        2.1    (API level 7)
        2.2    (API level 8)
        2.3    (API level 10)
        3.1    (API level 12)
        4.0    (API level 14)
        4.0.3  (API level 15)
        4.1    (API level 16)
        4.2    (API level 17)
        4.3    (API level 18)
        4.4    (API level 19)
        4.4.87 (API level 20)
Java SDK: C:\Program Files\Java\jdk1.6.0_39
java version "1.6.0_39"
Java(TM) SE Runtime Environment (build 1.6.0_39-b04)
Java HotSpot(TM) Client VM (build 20.14-b01, mixed mode, sharing)

=== Build Information ===

Release ID: 507000652
Git revision: 042e44ba92a6a9c46bd2b69b0b4348df43f381ea
Build date: 2014-12-11 16:21:38-05
Xamarin addins: 06d3aaafde7f726d508e079c9b297cc9aae4af55

=== Operating System ===

Windows 6.1.7601.65536

Note: Please confirm if you are still facing this issue using the latest builds. And if yes then it will be very helpful if you could please provide us with some more information such as:

1. Detailed Steps followed.
2. Build information
3. XVS logs: VS >> Help >> Zip Xamarin Logs

As of now marking this issue as needinfo.
Comment 2 Jose Gallardo 2016-12-22 19:18:23 UTC
I'll mark the bug as resolved not_reproducible.
Please feel free to reopen it if you can still reproduce the issue with current bits.