Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 20149 [details]
It seems that you need to corrupt one of the components in %localappdata%\Xamarin\Cache\Components
And then attempt to restore will give you the following
C:\Program Files\Far Manager>"C:\Build Agent\work\d7974c1f8dd35a08\Bin.ReSharperHost\xamarin-component.exe" restore C:\t
INFO (restore): Computed cookie jar path: C:\Users\builduser.WINDOWS-OE1VE3K\.xamarin-credentials
INFO (restore): [*] Restoring azure-mobile-services v1.3.1
INFO (restore): [*] Successfully restored azure-mobile-services v1.3.1
but no Components folder will be created near the sln file.
Created attachment 20150 [details]
my corrupted xam
Created attachment 20151 [details]
The latest version of Xamarin Component resolves this issue.
There is now an error message alerting thus user of the failed unzip.