Bug 588 - Identity/Provisioning Profile "autofix" is misplaced/confusing
Summary: Identity/Provisioning Profile "autofix" is misplaced/confusing
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 2.6 RC 1
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2011-09-01 18:42 UTC by Sebastien Pouliot
Modified: 2011-09-01 19:13 UTC (History)
2 users (show)

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:

Description Sebastien Pouliot 2011-09-01 18:42:08 UTC
It seems the iPhone addin will "autofix" the identity and/or provisioning profile when they cannot be found. This is great but semi-transparent and confusing. E.g.

Load and build an application (e.g. download) that has invalid (for your computer) entries. When you Debug/Deploy it you'll see something like:

Please ensure your device is connected...
Connected to: Neptune
This application has been signed with a provisioning profile which does not include this device
Connected to: Neptune
Installing application
Installation failed: AMDeviceInstallApplication returned: 0xe8000050
The application was terminated by a signal: SIGHUP

So you go look at the "iPhone Bundle Signing" options only to see them set to "Developer (automatic)" and "automatic" (no visual cue that have been "fixed" or modified). 

At this point you can look around a bit (looking for the culprit) until try again to debug/deploy only to realize that the error is gone.

I would be nicer to either:

a) warn that the settings are wrong and modified (when the "iPhone Bundle Signing" options are displayed);

b) fix this earlier (when project is loaded?) so the first build won't fail;

or something similar so the feeling is not "sometime it fails, sometime it works" :-)
Comment 1 Mikayla Hutchinson [MSFT] 2011-09-01 18:56:35 UTC
It doesn't ever alter the project options automatically. I'm not sure what you're describing.

What "automatic" means is that *at build time* it tries to find the most specific installed provisioning profile that matches the app ID. On your machine that could be one key, son someone else's machine it could be another.

Did you perhaps deploy a binary that had been *built* on someone else's machine?
Comment 2 Sebastien Pouliot 2011-09-01 19:13:57 UTC
I "always" use rebuild all when opening a solution but it would make sense I forgot to do so this time.

FWIW I don't think "automatic" is confusing to anyone ;-) and I'm glad there's no under-the-hood changes being made.