AppCode Configurations and XCode Schemes in latest EAP

Having xcode schemes that are automatically synched with AppCode's configurations is kind of confusing.  AppCode configurations specify a Target and a Destination (device/simulator) while Schemes really only specify a Target (along with some other settings) but NOT a destination.  

It seems to me that AppCode needs to have a destination selection as well as a scheme selection if the intent is to stay in sync with xcode.  The current behaviour of creating schemes for all my AppCode configurations creates a bunch of duplicate schemes.

For example, if I have two configurations:
  - TargetA - SIM  (runs TargetA on a simulator)
  - TargetA - DEVICE (runs TargetA on a device)

In the new EAP, this results in two schemes with the same names.  And the "SIM" and "DEVICE" are meaningless since xcode splits the target and destination selection.

Am I just not using configurations the way they were intended?

3 comments
Comment actions Permalink

Wayne,

you can use Run configurations as you use schemes - create a configuration for a target and, when necessary, change a destination (this will be easier when we implement http://youtrack.jetbrains.com/issue/OC-2826).

Though, if it is convenient, you can create separate configurations for a device and a simulator - we think, AppCode offer better flexibility here, since destination is associated with a run configuration.

Does this answer your question?

0
Comment actions Permalink

Though, if it is convenient, you can create separate configurations for a device and a simulator - we think, AppCode offer better flexibility here, since destination is associated with a run configuration.


This is exactly what I was doing and attempted to describe in my original post.  The problem is that AppCode is now taking the two configurations (one for device and one for simulator) and putting them into the xcode project as schemes.  This doesn't make sense as the two configurations essentially are the same when turned into schemes (as schemes do not have a destination).

OC-2826 would fix this problem totally as it would remove the need for multiple configurations in the first place.  I have voted for it.

Thanks for the reply and I guess I'll just have to live with a polluted scheme list in Xcode for a while :(.
0
Comment actions Permalink

Agreed. If AppCode is set up to use schemes, it needs to handle target device the same way XCode does. It got very confusing when AppCode added all the targets I had set up to the XCode schemes (and AppCode also appears to break custom build schemes, but I've added a separate JIRA for that issue).

0

Please sign in to leave a comment.