Bug 31651 - Unable to debug from windows (xamarin) machine to MAC Simulator or Device
Summary: Unable to debug from windows (xamarin) machine to MAC Simulator or Device
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: mdprasad
URL:
Depends on:
Blocks:
 
Reported: 2015-07-06 05:56 UTC by mdprasad
Modified: 2016-12-22 22:34 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Visual Studio cannot start the application automatically because it was signed with a Distribution provisioning profile. (8.04 KB, image/png)
2015-07-06 05:56 UTC, mdprasad
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description mdprasad 2015-07-06 05:56:19 UTC
Created attachment 11867 [details]
Visual Studio cannot start the application automatically because it was signed with a Distribution provisioning profile.

Hi, 

1. Xamarin Build Host has paired successfully. 
2. From Windows (Visual Studio) compiled successfully.
3. when we executing it is prompting error message.

Error Message: 
Please Start the Application

The application has been built and uploaded, or is already up to date.

Visual Studio cannot start the application automatically because it was signed with a Distribution provisioning profile. Please start it by tapping the application icon on the device.

I have a couple of question against Xamarin build host. Please answer to those.
https://forums.xamarin.com/discussion/44990/couple-of-questios-on-xamarin-ios-build-host#latest

Regards
M.D.Prasad
Comment 1 mag@xamarin.com 2016-05-11 18:13:13 UTC
Since we completely changed the way that Visual Studio connects to the Mac, I recommend to verify if the issues gets solved by using the new Xamarin Mac Agent. In addition, find below the answers to the questions:

1 - On every restart windows or mac machines, do we need to pair once again or not required?

- You only need to connect once to each Mac machine. Then, unless you forget the machine on the XMA Server dialog in Visual Studio, the connection will be performed automatically. If you need to change to another machine, you can do it directly via the connection dialog. To connect to a machine for the first time, you only need to enter your Mac credentials and Visual Studio will just connect (if the Mac machine meets the requirements to connect)

2 - Can we pair multiple windows machines to single Mac machine?

- Yes. You can connect multiple Windows machines to a single Mac and you can also connect multiple VS instances on the same Windows machine to a single Mac. In the case of connecting multiple machines, you should have different users configured in the Mac, and logged in by the time you will connect from Windows.

3 - How can we design UI from .xib files on windows machine (visual studio)?

- You can design both .xib and .storyboard files from Visual Studio just by opening the file inside VS and start adding controls to them.
Comment 2 Jose Gallardo 2016-12-22 22:34:26 UTC
Hi,
As we've added several improvements to our build system and deploying/debugging mechanism since the bug was reported, I'm resolving it tentatively as Fixed.
That said, if you're still facing this issue with current bits, please feel free to reopen the bug.
Thanks