Run/Debug Configuration
On this page:
- Basics
- Types of run/debug configurations
- Temporary configuration
- Permanent configuration
- Default run/debug configuration settings
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 run/debug configuration types for the various running, debugging and testing issues. The user can create his/her own run/debug configurations of specific types.
Each run/debug configuration type has its own default settings. Whenever a new run/debug configuration of the respective type is created, it is based on these default settings.
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 or 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 run/debug configuration settings
The default run/debug configuration settings appear in the Run/Debug configurations dialog box under the nodeDefaults. They denote the settings that are used when a new run/debug configurations is created.
You can set the default settings for a specific configuration type that will become applicable to any run/debug configuration of this type created later. Changing defaults does not affect the existing run/debug configurations.
The process of editing the per-type default configuration settings is described here. The process of creating or editing the custom run-debug configurations is described on the page Creating or Editing Run/Debug configurations.