Bug 2099 - A default configuration should use the distribution certificate
Summary: A default configuration should use the distribution certificate
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 2.8.2
Hardware: Macintosh Mac OS
: Lowest enhancement
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2011-11-20 13:41 UTC by Ian
Modified: 2012-04-24 12:37 UTC (History)
5 users (show)

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

Screen SHot showing error in cert assignment (132.78 KB, image/jpeg)
2011-11-20 13:41 UTC, Ian

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 Ian 2011-11-20 13:41:17 UTC
When you use the FILE-NEW-SOLUTION menu to choose a C#-iPhone-Tabbed application, the wizard creates a project that has the certificate chosen for "Developer" instead of "Release"

I have included a screen shot. In this example I just ran the wizard and went to Project Properties, that's all.

No cert exists yet, but even after I add a cert, it stays on Developer instead of Release.

I have the newest as of today MD and MT

This is a problem because it works fine for the developer, but when we create an IPA and upload it to our MDM provider, the developer can install it fine, but a tester or customer gets strange MDM errors because the wrong cert it used to build the release.

This caught us yesterday and took us a while to figure out what was happening as it works for the developers who have the dev cert on their phones.
Comment 1 Ian 2011-11-20 13:41:53 UTC
Created attachment 913 [details]
Screen SHot showing error in cert assignment
Comment 2 Mikayla Hutchinson [MSFT] 2011-11-20 18:37:46 UTC
This is by design. Typically, most developers on a project will not have access to the distribution key. The release configuration is intended for such developers to test release (non-debug) builds locally. For distribution (ad-hoc or appstore) you would typically create another configuration when you're ready to publish, and that would use the distribution key.

There are several ways I can think we could improve this, but I'm not sure which is best:
* Create appstore and adhoc configurations by default - though not all developers will want both, and they'll have to be manually kept in sync with the release config.
* Have the Release config use the Distribution cert, but fall back to Developer with a warning.
* Have a "publish" command that re-signs the app with the dist key.