AppCode 3.3 Help

Run/Debug Configuration

On this page:

Basics

AppCode enables using numerous run/debug configurations. Each run/debug configuration represents a named set of run/debug startup properties. When you perform run, debug, or test operations with AppCode, you always start a process based on one of the existing configurations using its parameters.

AppCode comes with a number of predefined (default) run/debug configuration types for the various running, debugging and testing issues.

Whenever a new run/debug configuration is created, it is based on these default settings applicable to any new configuration of the respective type.

Types of run/debug configurations

Run configurations in AppCode is an equivalent of Xcode schemes and they are kept synced with Xcode schemes.

Temporary configuration

A temporary run/debug configuration is automatically created every time you choose Run <item_name> or Debug <item_name> for an item without a permanent configuration. Temporary configurations can be saved as permanent.

Temporary configurations are marked with semi-transparent icons and are managed same way as the permanent configurations.
By default, 5 temporary configurations are allowed per project. You can change this limit via the Edit Configurations dialog.

Permanent configuration

A configuration of this type is explicitly created or taken from the corresponding schemes, if you are working with an existing Xcode project.

Default vs custom run/debug configurations

The default run/debug configurations appear in the Run/Debug configurations dialog box under the node Defaults. They denote the profiles against which the custom run/debug configurations are created.

When you change the default run/debug configurations, you thus change the settings that will become applicable to any run/debug configuration of the corresponding type created later. Changing defaults does not affect the existing run/debug configurations.

The process of editing the default run-debug configurations if described here. The process of creating or editing the custom run-debug configurations is described on the page Creating or Editing Run/Debug configurations.

See Also

Last modified: 10 February 2016