Flutter IntelliJ Plugin M43 Release

[Steve Messick]

Flutter IntelliJ Plugin M43 Release

Hot Reload on Save Improvements

We’ve tweaked the behavior of hot reload on save. Previously, we wouldn’t try a reload if there were analysis errors in the project; this was under the assumption that the errors would be significant enough that you wouldn’t want an automatically triggered reload.

We’ve removed that restriction - now, a save will trigger a hot reload even if there are analysis errors in the project. Since initially rolling out hot reload on save, hot reload has both gotten faster, and the quality of the compilation errors from the VM have improved - we can rely on the VM reporting good errors if there are any issues blocking reload.

In addition, we addressed an issue with the reload on save mechanism where it could stop working for that IntelliJ session; requiring a restart of IntelliJ.

Dev Channel

We’re launching an early-access version of the plugin, called the dev channel. This version will be updated weekly, containing all changes made in the previous week. To use it you need to configure IntelliJ or Android Studio to look for plugins on the dev channel repository.

Open the Plugins preference page (Mac) or settings page (Windows, Linux). Click the gear at the top-right and select Manage Plugin Repositories.

A list editor will pop up that allows you to edit custom plugin repositories. Add this to the list:

https://plugins.jetbrains.com/plugins/dev/list

Then click OK. The version of the Flutter plugin you see in the Marketplace list will be the dev channel version.

And...

• We’ve added support for IntelliJ 2020.1 EAP.

• We’ve added an ‘Open DevTools’ menu item to the Tools > Flutter menu to improve the discoverabilty of opening DevTools.

• Implemented several fixes to the FPS calculation in the Flutter Performance tool window.

• In the analysis server - not yet available to all clients - we’ve added improvements to code completion, including things like completing closures for named parameters ( #25267, #40013, #40202).

Additional Bug Fixes

The change log has a list of bugs that were fixed in this release.

Android Studio Canary

Canary versions of Android Studio are not officially supported. The dev channel (see above) will be used to distribute versions of the plugin that work with canary builds.

Known Issues

The IDE support for add-to-app does not work well in Android Studio 3.5. We’re expecting 3.6 to become the stable version any day now, and these features do work in 3.6.

[Benedicte Roussel]

Hello Steve,

This update sounds quite nice, gradle is nice.

I am on Windows and AndroidStudio(stable), the IDE suggested the update so I have done it.

1 _  Since a while when I was launching an app some grey windows were appearing everywhere, now it does no longer happen -good point here-

2_   Since a while I had to change this line :

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    flutterRoot ='Flutter SDK not found. Define location with flutter.sdk in the local.properties file.'
}

I still have to do it

3_  to avoid inconstancy with the IDE and emulator, I still tend to update the kotlin version:

buildscript {
    ext.kotlin_version = '1.3.61'
    repositories {
        google()
        jcenter()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.3'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }
}

As far as the Android part is concerned I tend to keep it update too:

android {
    compileSdkVersion 29

targetSdkVersion 29

androidTestImplementation 'androidx.test:runner:1.2.0'
androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0'

4_ I have a question here:

when launching the demo app with  flutter run -d chrome, i have now this /[::1], is that normal?     ( http://[::1]:XXXXX/#/)

Thanks

--
You received this message because you are subscribed to the Google Groups "Flutter Development (flutter-dev)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flutter-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/flutter-dev/bec74afe-60ff-4211-833b-7b3e00a88363%40googlegroups.com.