Bug 52977 - [XVS 2017-Dev15 RTW] Option to update outdated component not available
Summary: [XVS 2017-Dev15 RTW] Option to update outdated component not available
Alias: None
Product: Components
Classification: Xamarin
Component: Component Store ()
Version: N/A
Hardware: PC Windows
: --- major
Target Milestone: ---
Assignee: Bill Holmes
Depends on:
Reported: 2017-03-02 16:32 UTC by Jacky Waswani
Modified: 2017-06-23 19:09 UTC (History)
3 users (show)

Tags: bb
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 Jacky Waswani 2017-03-02 16:32:09 UTC
Option to update outdated component not available.

1.Create an Android application.
2.In the solution explorer, click on "Components" and add any component which is not the latest version but an older version. (Need to be logged in with Xamarin account).
3.Once component is added to app, try finding option to update the added component.

Expected Result:
Option to update outdated component should be available.

Actual Result:
No option available to update outdated component.

Screencast link:
Comment 1 Bill Holmes 2017-03-02 18:34:25 UTC
You are able to update a component by visiting the store, browsing to the component and clicking the update button.  

It is not an ideal scenario for update I agree.  However we have discussed internally making this improvement many times and it gets denied due to resource constraints and the fact that it is possible for the user to update.