Using JetBrains Chrome Extension
On this page:
- Installing the JetBrains Chrome extension
- Working with JetBrains Chrome extension
- Overriding the default CORS settings
- Changing port
Installing the JetBrains Chrome extension
You can install the extension during the first debugging session with Chrome or Dartium or at any time directly from the Chrome Web Store.
- Open the JetBrains IDE Support page by doing one of the following:
- Visit the Chrome Web Store at any time.
- Click the Add to Chrome button .
- In the Confirm New Extension dialog box that opens, click Add. The Add to Chrome button changes to Added to Chrome .
When the extension is installed, the icon is displayed next to the Chrome address bar.
Working with JetBrains Chrome extension
Control over the JetBrains Chrome extension is provided through the chrome://extensions page:
- To open the page, just type
chrome://extensionsin the Chrome address bar.
Alternatively click Customize and control Google Chrome (), choose Settings on the context menu, and then click Extensions on the chrome://settings page that opens.
- To deactivate the extension, clear the Enabled check box. The check box name changes to Enable.
- To activate the extension, select the Enable check box.
- To uninstall the extension, click the Remove from Chrome button .
Overriding the default CORS settings
Suppose the page you are debugging requests a resource which is protected against access for security reasons through CORS settings. You can enable access to the resources protected by default by changing the Chrome extension options.
To override the default CORS settings:
- Right-click and choose Options on the context menu. A web page with Chrome extension options opens showing the parameters to connect to AppCode.
- In the Force CORS text box, type the pattern that defines the URL addresses you want to make accessible, for example:
During a debugging session, the Chrome extension listens to the port of the JetBrains IDE from which the extension was invoked. Each IDE including AppCode has its own default port on which it starts by default.
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 (for example,
current port 63343):
To fix the problem, specify the actual AppCode port in the Chrome extension options:
- Right-click and choose Options on the context menu. A web page with the Chrome extension options opens showing the parameters to connect to AppCode.
- In the IDE Connection area, specify the actual AppCode port in the Port spin box.