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:
1. Open VS.
2. Create or open any iOS application.
3. Connect to build host.
4. Observe that build host is connected to VS.
5. now debug or run the application on physical device using VS.
Actual Result: Getting build errors related to provisioning profile(unable to fetch provisioning profile) This is the gist for the same: https://gist.github.com/saurabh360/174b84e364a645023822 . However, If we go to project properties the in iOS Bundle Signing we are not seeing all provisioning profile. while we are logged in on mac server with valid developer account and we are successfully able to deploy and launch application on physical device using XS on Mac.
User should able to deploy and launch application on physical device using VS.
mtbserver log: https://gist.github.com/saurabh360/99d31edabfce6ec4f0d2
mac server log: https://gist.github.com/saurabh360/d95275bf7aae8a850e7e
iOS for VS 1.6.81
This is working fine with X.iOS 188.8.131.52
I am unable to replicate this. 184.108.40.206 and the latest mtvs-1.6-series
Can you attach the project that causes this issue?
Today I have checked this issue with following builds:
iOS for VS 1.6.84
Now we are successfully able to deploy and launch application on build host using VS.
Hence closing this issue.