Bug 12296 - Every time I add a file to a project, my configuration mappings are lost
Summary: Every time I add a file to a project, my configuration mappings are lost
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2013-05-18 13:42 UTC by Jackson Harper
Modified: 2013-12-05 18:36 UTC (History)
1 user (show)

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

screenshot (26.39 KB, image/png)
2013-05-18 13:42 UTC, Jackson Harper
step one (80.57 KB, image/png)
2013-05-18 15:09 UTC, Jackson Harper
step two (104.36 KB, image/png)
2013-05-18 15:10 UTC, Jackson Harper
step three (107.32 KB, image/png)
2013-05-18 15:10 UTC, Jackson Harper
error again (16.72 KB, image/png)
2013-05-18 15:11 UTC, Jackson Harper

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 Jackson Harper 2013-05-18 13:42:56 UTC
Created attachment 3986 [details]

Using XS 4.0.8 (build 2)

Every time I add a file to my project, I get an (invalid configuration mapping) error in my source tree (see attached image).

To fix, I have to go into Project Options, Configurations and choose Debug|iPhoneSimulator.

Also note: if I do that twice in a row, the second time I will get the warning again. So if I do not have the warning, go into configurations and set the configuration to Debug|iPhoneSimulator (which it is already set to) I will get the error.

If I choose Debug|iPhone, the error will go away, but my target will still be set to iPhone Simulator. I can manually change that though.
Comment 1 Jackson Harper 2013-05-18 13:45:00 UTC
This actually seems to happen any time my configuration is touched. Like I just changed a file's build action and the error came up again.
Comment 2 Mikayla Hutchinson [MSFT] 2013-05-18 15:07:31 UTC
What this means is that your solution configuration is mapped to a project configuration that no longer exists. You can fix the mapping in the Solution Options-> Configurations-> Configuration Mappings. The invalid one will be colored red.

Could you please clarify what you mean by "go into Project Options, Configurations and choose Debug|iPhoneSimulator"?
Comment 3 Jackson Harper 2013-05-18 15:09:21 UTC
Going to attach a series of screenshots, just so I don't describe it wrong:
Comment 4 Jackson Harper 2013-05-18 15:09:50 UTC
Created attachment 3987 [details]
step one
Comment 5 Jackson Harper 2013-05-18 15:10:14 UTC
Created attachment 3988 [details]
step two
Comment 6 Jackson Harper 2013-05-18 15:10:34 UTC
Created attachment 3989 [details]
step three
Comment 7 Jackson Harper 2013-05-18 15:11:06 UTC
Created attachment 3990 [details]
error again
Comment 8 Mikayla Hutchinson [MSFT] 2013-05-19 00:34:24 UTC
Selecting the item in the list of configurations in project options only changes what the buttons on the right affect, it doesn't actually change anything. What do the configuration mappings in the solution options show?
Comment 9 Mikayla Hutchinson [MSFT] 2013-05-20 13:02:18 UTC
Can you confirm that fixing the mapping in the Solution Options fixes the issue?

If so, then the bug here is that the error goes away when it shouldn't.
Comment 10 PJ 2013-11-19 17:05:37 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 11 PJ 2013-12-05 18:36:04 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.