On this page:
- Open the Debugger page: choose and in the Preferences dialog box that opens, click Debugger under Build, Execution, Deployment.
- On the Debugger page that opens, specify the following:
Use the Built-in server port spin-box to
specify the number of the port where the built-in web server runs. The port number should be set to
1024 or higher. By default this port is set to the default AppCode port through which AppCode
accepts connections from services (
63342). During a debugging session, the Chrome extension will listen to this port. If for some reason the default AppCode port is already busy, AppCode finds the closest available port and starts on it. This results in a conflict: AppCode is running on a "new" port while the Chrome extension still listens to the port of a previously started product and fails to establish connection with AppCode. The conflict reveals when you initiate a debugging session from AppCode: the extension fails to connect through the default port, AppCode waits for connection from the extension and displays the following message with the port number where it is actually running:
To fix the problem, specify the actual port in the Chrome extension options, see Using JetBrains Chrome Extension.
- In the Value tooltip delay (ms) field of the Data Views page , specify the time period between pointing at an object and displaying the object's value in a tooltip.
- Use the Built-in server port spin-box to specify the number of the port where the built-in web server runs. The port number should be set to 1024 or higher. By default this port is set to the default AppCode port through which AppCode accepts connections from services (