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 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.
# Steps to reproduce
Xamarin Update : Install Update (only Workbooks & Inspector1.2.0-rc.2 is listed)
# Expected behavior
Succesful install and not to be re-prompted to install Workbooks & Inspector again... endless cycle
# Actual behavior
Error Dialog (Xamarin Update : Error : Package failed to install) after receiving receiving the Xamarin Workbooks & Inspector1.2.0-rc.2 installation was successful dialog (Summary step)
# Test environment (full version information)
Xamarin Studio Community Version 6.3 (build 831)
Xamarin Inspector Version: 1.2.0-rc.2Hash: 15b00be Branch: d15-1 Build date: Mon, 06 Mar 2017 15:58:04 GMT
Created attachment 20282 [details]
Successful installation Summay step
Created attachment 20283 [details]
Error Package failed to install
I'm seeing this as well.
Robert, Cody, what version of macOS are you on, and what was the previously installed version of Workbooks & Inspector?
And can you confirm the version in the about box of Workbooks?
Based on the fact that you're seeing:
Build date: Mon, 06 Mar 2017 15:58:04 GMT
It did install correctly and is a duplicate of #53160 (see this bug for details on the reason/resolution).
If this is not the case, please reopen.
*** This bug has been marked as a duplicate of bug 53160 ***