An IntelliJ plugin for Flutter development. Flutter is a new mobile app SDK to help developers and designers build modern mobile apps for iOS and Android.
Android Studio and M18.3: Using version 18.3 of the plugin with Android Studio? See this known issue for help upgrading from that version.
Flutter's hot reload helps you quickly and easily experiment, build UIs, add features, and fix bugs faster. Experience sub-second reload times, without losing state, on emulators, simulators, and hardware for iOS and Android.
A brief summary of the getting started guide:
- install the Flutter SDK
flutter doctorfrom the command line to verify your installation
- ensure you have a supported IntelliJ development environment, either:
- IntelliJ 2017.3 or 2018.1, Community or Ultimate Edition, or
- Android Studio 3.0 (note: Android Studio 3.1 Beta is currently not supported)
- open the plugin preferences
Preferences > Pluginson macOS,
File > Settings > Pluginson Linux, select "Browse repositories…"
- search for and install the 'Flutter' plugin
- choose the option to restart IntelliJ
- configure the Flutter SDK setting
File>Settingson Linux, select
Languages & Frameworks > Flutter, and set the path to the root of your flutter repo
Please use our issue tracker for Flutter IntelliJ issues.
- for more general Flutter issues, you should prefer to use the Flutter issue tracker
- for more Dart IntelliJ related issues, you can use JetBrains' YouTrack tracker
Please note the following known issues:
- If you are using version 18.3 of the Flutter plugin with Android Studio, it will not upgrade to newer versions of the plugin. In order to upgrade, you'll need to uninstall the plugin and re-install it (this can be done from the plugins preference page).
- #601: IntelliJ will read the PATH variable just once on startup. Thus, if you change PATH later to include the Flutter SDK path, this will not have an affect in IntelliJ until you restart the IDE.
- We are seeing occasional timeouts when trying to connect to Observatory when debugging against the iOS simulator; restarting the simulator should get you back on track.