Bug 6503 - aps-environment in entitlements should be driven from build configuration
Summary: aps-environment in entitlements should be driven from build configuration
Status: RESOLVED NORESPONSE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 3.0.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-08-11 01:44 UTC by t9mike
Modified: 2013-11-19 17:06 UTC (History)
1 user (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 NORESPONSE

Description t9mike 2012-08-11 01:44:26 UTC
In Entitlements.plist, aps-environment can vary between "production" and "development." It would be good to have this configurable via project options so that it will change automatically when switching build configuration.
Comment 1 Jeffrey Stedfast 2013-06-07 13:22:04 UTC
You can have a different Entitlements.plist file per build configuration

Does that solve your issue?
Comment 2 PJ 2013-11-19 17:04:19 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 t9mike 2013-11-19 17:06:58 UTC
My apologies. Jeffrey's suggestion was fine. You can close.