• Android Studio and IntelliJ
• Visual Studio Code

Follow the Set up an editor instructions to install the Dart and Flutter extensions (also called plugins).

Updates to the extensions are shipped on a regular basis. By default, VS Code automatically updates extensions when updates are available.

To install updates manually:

1. Click the Extensions button in the Side Bar.
2. If the Flutter extension is shown with an available update, click the update button and then the reload button.
3. Restart VS Code.

There are a couple ways to create a new project.

To create a new Flutter project from the Flutter starter app template:

1. Open the Command Palette (Ctrl+Shift+P (Cmd+Shift+P on macOS)).
2. Select the Flutter: New Project command and press Enter.
3. Select Application and press Enter.
4. Select a Project location.
5. Enter your desired Project name.

To open an existing Flutter project:

1. Click File > Open from the main IDE window.
2. Browse to the directory holding your existing Flutter source code files.
3. Click Open.

The Flutter extension performs code analysis that enables the following:

• Syntax highlighting
• Code completions based on rich type analysis
• Navigating to type declarations (Go to Definition or F12), and finding type usages (Find All References or Shift+F12)
• Viewing all current source code problems (View > Problems or Ctrl+Shift+M (Cmd+Shift+M on macOS)) Any analysis issues are shown in the Problems pane:
  {:.mw-100.pt-1}

{{site.alert.note}} You can debug your app in a couple of ways.

• Using DevTools, a suite of debugging and profiling tools that run in a browser. DevTools replaces the previous browser-based profiling tool, Observatory, and includes functionality previously only available to Android Studio and IntelliJ, such as the Flutter inspector.
• Using VS Code's built-in debugging features, such as setting breakpoints.

The instructions below describe features available in VS Code. For information on using launching DevTools, see Running DevTools from VS Code in the DevTools docs. {{site.alert.end}}

Start debugging by clicking Run > Start Debugging from the main IDE window, or press F5.

When a Flutter project is open in VS Code, you should see a set of Flutter specific entries in the status bar, including a Flutter SDK version and a device name (or the message No Devices):
{:.mw-100.pt-1}

{{site.alert.note}}

• If you do not see a Flutter version number or device info, your project might not have been detected as a Flutter project. Ensure that the folder that contains your pubspec.yaml is inside a VS Code Workspace Folder.
• If the status bar reads No Devices, Flutter has not been able to discover any connected iOS or Android devices or simulators. You need to connect a device, or start a simulator or emulator, to proceed. {{site.alert.end}}

The Flutter extension automatically selects the last device connected. However, if you have multiple devices/simulators connected, click device in the status bar to see a pick-list at the top of the screen. Select the device you want to use for running or debugging.

{{site.alert.secondary}} Are you developing for macOS or iOS remotely using Visual Studio Code Remote? If so, you might need to manually unlock the keychain. For more information, see this question on StackExchange.

{{site.alert.end}}

1. Click Run > Start Without Debugging in the main IDE window, or press Ctrl+F5. The status bar turns orange to show you are in a debug session.
   {:.mw-100.pt-1}

1. If desired, set breakpoints in your source code.

2. Click Run > Start Debugging in the main IDE window, or press F5.

   • The left Debug Sidebar shows stack frames and variables.
   • The bottom Debug Console pane shows detailed logging output.
   • Debugging is based on a default launch configuration. To customize, click the cog at the top of the Debug Sidebar to create a launch.json file. You can then modify the values.

Flutter offers many different build modes to run your app in. You can read more about them in Flutter's build modes.

1. Open the launch.json file in VS Code.

   If you do not have a launch.json file, go to the Run view in VS Code and click create a launch.json file.

2. In the configurations section, change the flutterMode property to the build mode you want to target.

   • For example, if you want to run in debug mode, your launch.json might look like this:

    "configurations": [
     {
       "name": "Flutter",
       "request": "launch",
       "type": "dart",
       "flutterMode": "debug"
     }
   ]

3. Run the app through the Run view.

Flutter offers a best-in-class developer cycle enabling you to see the effect of your changes almost instantly with the Stateful Hot Reload feature. See Using hot reload for details.

You might find the following advanced debugging tips useful:

During a debug session, several additional debugging commands are added to the Command Palette and to the Flutter inspector. When space is limited, the icon is used as the visual version of the label.

**Toggle Baseline Painting** {:width="20px"}

Causes each RenderBox to paint a line at each of its baselines.

**Toggle Repaint Rainbow** {:width="20px"}

Shows rotating colors on layers when repainting.

**Toggle Slow Animations** {:width="20px"}

Slows down animations to enable visual inspection.

**Toggle Debug Mode Banner** {:width="20px"}

Hides the debug mode banner even when running a debug build.

By default, debugging an external library is disabled in the Flutter extension. To enable:

1. Select Settings > Extensions > Dart Configuration.
2. Check the Debug External Libraries option.

If you have additional tips we should share, let us know!

Assists are code changes related to a certain code identifier. A number of these are available when the cursor is placed on a Flutter widget identifier, as indicated by the yellow lightbulb icon. The assist can be invoked by clicking the lightbulb, or by using the keyboard shortcut Ctrl+. (Cmd+. on Mac), as illustrated here:

{:width="467px"}

Quick fixes are similar, only they are shown with a piece of code has an error and they can assist in correcting it.

Wrap with new widget assist : This can be used when you have a widget that you want to wrap in a surrounding widget, for example if you want to wrap a widget in a Row or Column.

Wrap widget list with new widget assist : Similar to the assist above, but for wrapping an existing list of widgets rather than an individual widget.

Convert child to children assist : Changes a child argument to a children argument, and wraps the argument value in a list.

Convert StatelessWidget to StatefulWidget assist : Changes the implementation of a StatelessWidget to that of a StatefulWidget, by creating the State class and moving the code there.

Snippets can be used to speed up entering typical code structures. They are invoked by typing their prefix, and then selecting from the code completion window: {:width="100%"}

The Flutter extension includes the following snippets:

• Prefix stless: Create a new subclass of StatelessWidget.
• Prefix stful: Create a new subclass of StatefulWidget and its associated State subclass.
• Prefix stanim: Create a new subclass of StatefulWidget, and its associated State subclass including a field initialized with an AnimationController.

You can also define custom snippets by executing Configure User Snippets from the Command Palette.

Hot reload : During a debug session, clicking the Hot Reload button on the Debug Toolbar, or pressing Ctrl+F5 (Cmd+F5 on macOS) performs a hot reload.

Keyboard mappings can be changed by executing the Open Keyboard Shortcuts command from the Command Palette.

Hot reload works by injecting updated source code files into the running Dart VM (Virtual Machine). This includes not only adding new classes, but also adding methods and fields to existing classes, and changing existing functions. A few types of code changes cannot be hot reloaded though:

• Global variable initializers
• Static field initializers
• The main() method of the app

For these changes, fully restart your application without having to end your debugging session. To perform a hot restart, run the Flutter: Hot Restart command from the Command Palette, or press Ctrl+Shift+F5(Cmd+Shift+F5 on macOS).

All known bugs are tracked in the issue tracker: Dart and Flutter extensions GitHub issue tracker.

We welcome feedback, both on bugs/issues and feature requests. Prior to filing new issues:

• Do a quick search in the issue trackers to see if the issue is already tracked.
• Make sure you are up to date with the most recent version of the plugin.

When filing new issues, include flutter doctor output.