Flutter IntelliJ Plugin M45 Release
Steve Messick
Flutter IntelliJ Plugin M45 Release
Android Studio Canary in the Dev channel
We added best-effort (unofficial) support for canary versions of Android Studio to the dev channel. Please use our plugin’s dev channel, not the regular stable release. Due to version number overlap, the canary builds can get confused with the beta builds. If you install a beta version of the plugin from the stable channel into a canary version of Android Studio some features will not work. We’re looking for a way to make it impossible to install the beta version into the canary platform but it currently cannot be prevented.
The dev channel was announced previously; instructions for switching from stable to dev are in the Dev channel page. Note that releases to the dev channel are fully automatic - a new version is published every Sunday AM from the latest project source in github.
Support for IntelliJ 2020.1 RC 1
We now support IntelliJ 2020.1 RC 1; enjoy!
Improvements to how we display Flutter errors
We’d previously launched some work to make Flutter framework errors in user code more understandable (see Improving Flutter’s Error Messages).
One of the things that we did as part of that work was to show the full details for an initial error after a hot reload, but to show shorter summaries of all subsequent errors. This was because many of the errors were essentially a cascade from the first error. Typically this is something like overflow errors caused by the framework trying to display a diagnostic for the original error in-line in your app.
From feedback, we realized that this summarization was too aggressive. We’ve since changed the logic to show the full details for the first error after a frame is created, but to summarize the other errors that happen during that same frame. We think this better matches up with how these errors are created.
For example, from the Flutter error sample app, navigating to the material error, then the overflow error, you can see now that the overflow triggered by the material error is summarized, but the later overflow from the overflow page is not.
Other fixes and improvements
Along with a few other fixes, we addressed an issue where stack trace entries in the test execution console were not hyperlinked properly; you should now see hyperlinks back to the source for exceptions and test failures.
Regression in add-to-app support with Android Studio 4.0 beta
When adding a Flutter module to an Android app using Android Studio 4.0 beta the Flutter module files may not all show up in the Project view. If the module is created as a child directory of the Android app then everything works as expected. However, if the Flutter module is not a child of the app then its non-Android files do not show up.
Wayne Werner
pubspec.yamlIt used to show "
Pub get Pub upgrade Flutter upgrade Flutter doctor". Now, "
Flutter upgrade" is missing.
I've found having all four of these commands at my fingertips very useful, especially in the earlier phases of project development. I can only assume that losing the upgrade option is a bug.
Thanks,
Wayne