Brackets not working for you? Consider the following tips.
Make sure you download one of the "brackets-sprint-XX.dmg" (Mac) or "brackets-sprint-XX.msi" (Windows) installers from the Downloads page.
Some Windows Vista computers will block installers downloaded from the Internet, so nothing at all happens when you try to run the installer. To work around this: right-click the installer file, choose Properties, and click the Unblock button.
This can happen on some Windows machines. To work around this, try executing the installer from an elevated command prompt:
cdto the folder containing the installer.
msiexec /i "brackets-sprint-xx-WIN.msi"(where "xx" is the sprint number)
The Brackets app is not yet signed, so depending on your security settings you might get a message saying you can't run an application from an unknown developer. If so, you'll need to Ctrl-click on the application and choose "Open", then click on the "Open" button in the dialog that comes up.
If Brackets won't launch, check the permissions of the main executable files (e.g. using
ls -l). On Mac:
To fix permissions, use a command like
chmod +x bin/mac/Brackets.app/Contents/MacOS/Brackets.
Some archiving programs, such as Keka don't appear to preserve file permissions when unarchiving zip files. (More info here). If you run into this issue on Mac, try to unarchive the zip file by using Finder.
If you had previously used Brackets, your cache may have information that is conflicting with the most recent version. Find your cache folder and delete the cache. Warning: this will reset all of your Brackets preferences.
Next, try running Brackets from the command line. Open up a Terminal (or Command Prompt in Windows), navigate to the executable, and run Brackets. (On Mac, type
open bin/mac/Brackets.app.). Did an error appear? If so, file an issue or find us on IRC or the mailing list and we'll try to figure it out.
Currently, Live Development works differently for different types of files:
See How to Use Brackets for more details.
You can use
File > Open to open any file on your computer, but Brackets' definition of a project are the files in the folder opened using
File > Open Folder.... Some (but not all) Live Development features require a node server, which means being in the current project, so make sure the files that you want to use with Live Development are in the current project.
The Theseus extension is known to cause problems with Live Preview, and other extensions could potentially interfere also. Use
Debug > Reload Without Extensions to quickly see if the problem is being caused by an extension.
Brackets pauses sending updates to browser when it detects an HTML Syntax Error. In this case, it should color the line number in red (but this can be scrolled out of view) so scroll through entire page to verify that there are no highlighted line numbers.
The Live Preview lightning bolt icon should be also colored red and have a tooltip of "Live Preview (not updating due to syntax error)" in this case, but there's a known bug being tracked as issue #7126 where this sometimes doesn't happen. See issue #7126 for an illustrated description including the line number and icon coloring.
There is an issue regarding "Live Preview can never update if initially launched with syntax error", so after fixing a syntax error, try stopping and restarting Live Preview.
To use a local server, you need to specify a Base URL in the
File > Project Settings... dialog (see How to Use Brackets for details).
If you're using a local server and are seeing these messages such as "Oops! Google Chrome could not connect to localhost:[port]" (in Chrome) or "Unable to load Live Development page" (in Brackets), verify that your local server has been started.
As noted above, live HTML updating is disabled when using your own custom local server.
If you get the error
An error occurred when launching the browser. (error 2) when doing Live Development, installing Chrome for multiple user accounts may solve the issue.
If you keep getting errors when trying to launch Chrome, or if you keep getting prompted to restart Chrome, try rebooting your machine. Rebooting has resolved many odd issues with Live Development.
Try leaving an extra blank tab open in the instance of Chrome that is launched by Live Preview. This prevents Chrome from shutting down and restarting between each file, so Live Preview will launch faster; this may reduce some intermittent errors.
If Brackets cannot launch the Chrome browser on your Windows system, check the Registry setting here:
This is the file path that Brackets uses to launch Chrome. If this is not correct, then try reinstalling the Chrome browser at this location.
On Windows, you may run into issues starting Live Preview if you installed Chrome after installing Brackets. In that case, re-installing Brackets should fix the problem.
This section discusses some of the features that can affect performance and possible solutions.
On Mac OS 10.9 (Mavericks), Activity Monitor will say the Brackets Helper process is "Not Responding" even when it is working normally (bug #5794). You can safely ignore this unless Brackets is actually failing to respond when you click or type text.
Most Brackets extensions don't impact performance, but some may slow down Brackets (for example Show Whitespace can cause slow typing performance). Try
Debug > Reload Without Extensions to quickly check if the problem is being caused by an extension.
Using "Find in Files" and "JS Code Hinting" can be slow because of the number of files that are searched. You can try installing the experimental Exclude Folders extension to limit the number of folders that are searched.
This feature can negatively impact scrolling performance, so try turning it off with: View > Highlight Active Line
Debug > Reload Without Extensions to quickly check whether the problem is being caused by an extension. To re-enable your extensions, just quit and relaunch Brackets, or choose Debug > Reload With Extensions.
If this fixes the problem, you can identify the problematic extension by re-enabling extensions one-by-one:
Alternative: Select Debug > Show Developer Tools and look at the console. If an error message is present, it may have a link to the code that is failing, which in turn may point out a specific extension.
Debug > Show Developer Tools to open an instance of the Developer Tools for Brackets. If you've used the Developer Tools in Chrome this will look familiar. Check the Console tab for errors.
There's a known issue with the Webroot Identity Shield software blocking Paste in Brackets. If you're running Webroot, try the workarounds on their support page. (Fully up-to-date Webroot should no longer treat Brackets as "unknown"; try reinstalling to update your copy).
Last edited by Peter Flynn,