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.
Created attachment 16009 [details]
Visual Studio log file
Hi! I'm trying to use Xamarin from VS connecting to my MBP running OS X 10.11.4, both systems have all the available updates installed and Xamarin Studio and VS Extension are running Stable channel, both updated. I've attached my log from VS to the bug. I'm trying to overcome it for more than half of the year, so would appreciate any help :)
I think this is just fallout from a provisioning profile issue. The root problem seems to be:
Xamarin.Messaging.Client.MessagingClient Error: 0 : [2016-05-16 15:09:01.8700] An error occured on client vs11976andre while executing a post for topic xvs/idb/220.127.116.11/get-provisioning-profiles
Reassigning to the iOS component for now. If there is a problem on the designer side please reassign it back!
I'm not really sure if that is provisioning fault, because I can sign my apps and debug them on personal iPhone without any problems.
Just installed latest stable update with designer 18.104.22.168 and finally (I'm literally on the seventh sky).
Sorry, forgot to finish message. And finally was able to connect from VS to my Mac without any errors.
I mark this issue as Resolved according to the Comment 4. Please feel free to re open the bug if you still experience any related issue.