Bug 60300 - TFS Build erroring on - The specified iOS provisioning profile 'XXXX' could not be found
Summary: TFS Build erroring on - The specified iOS provisioning profile 'XXXX' could n...
Status: RESOLVED DUPLICATE of bug 60299
Alias: None
Product: iOS
Classification: Xamarin
Component: MSBuild ()
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-10-20 20:08 UTC by Tony
Modified: 2017-10-20 23:34 UTC (History)
2 users (show)

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

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 or GitHub 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 DUPLICATE of bug 60299

Description Tony 2017-10-20 20:08:33 UTC
When trying to run the build agent running on our mac from our TFS Build Server it fails with the following error:

The specified iOS provisioning profile 'XXXX' could not be found

However, I can successfully build it in Visual Studio 2015 from windows when connected to the mac. 

It even pulls the specific provisioning profile when connected. I have tried by specifying the profile and by setting it to Automatic with no luck either way. HELP!!!!
Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2017-10-20 23:34:53 UTC

*** This bug has been marked as a duplicate of bug 60299 ***