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:
Condition: build host should not have license on disk
1. Open VS.
2. Connect VS to build host.
3. Open or create iOS application.
4. Observe that a popup appears to activate license on build host.
5. Click on Activate button.
Actual Result: When user click on Activate button, it is not opening monotouch activation on build host and showing build error in VS "Failed to launch application com.xamarin.monotouchactivation". However, after some action like restarting VS when we again click on Activate button, VS get crashed this is the gist for the same: https://gist.github.com/AkhileshKumar01/d5b54d1821989ad1c44a
Note: This thing is happening when we have downgraded Xamarin.iOS for VS from 1.8.31 to 1.6.146 on VM. while we are not able to reproduce this on physical windows machine.
Expected Result: User should able to activate license on build host after clicking on 'Activate' button.
Mac Server log: https://gist.github.com/AkhileshKumar01/99d2323129fc6cafd647
Windows 8 VM
iOS for VS 1.6.146
Uninstalling 1.8 does not remove Xamarin/Shell/1.0.0/* from C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions
It is properly removed from C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions
See screencast: http://screencast.com/t/6T9EaUQEiMs
This causes all sorts of pain when undetected, so getting this bug fixed is high priority for testing.
PeterC we should have a case that should catch this on the QAVS lanes, CCing you.
On whatever machine it happened, can you start regedit.exe and navigate to the following key:
If there are any assemblies there which belong to us, remove them. From that point on uninstallation should work fine. Users won't have that problem since they never installed the "bad" 1.6 or 1.8 series from before this issue was fixed.
If the fix works, please close the bug, switching to NEEDINFO for now.
This solution works for me.
I'll email dev about it.
Today we have checked this issue on following builds :
iOS for VS 1.8.106
Now user is able to activate license on build host after clicking on 'Synchronize' button via VS.
Hence verifying this issue.