Flutter beta testing
See original GitHub issueDownload v1.5.0-beta.flutter.5 here
If testing, please post feedback in this thread including which platform you were testing on (Win/Mac/Linux). Any problems/issues can be raised as new issues but general feedback (even if everything works) is encouraged to help gauge stability (esp on platforms I can’t test).
Since there may be updates to this beta version, you may wish to subscribe to this thread to get notifications
Installing
- Uninstall any existing version of Dart Code from Code and restart Code
- Download the vsix from the link above
- Run the
Extensions: Install from VSIX
command from the Code command palette and browse to the downloaded vsix file - Restart Code again
Note: To revert to the marketplace version of the extension you will need to uninstall the beta version explicitly first.
Some things to test
If you test any of these any they work, please let me know (and on which platform)!
Windows
- Flutter projects are detected as flutter and the Dart SDK version number in the status bar (right) shows that it’s the Flutter version
- Standard Dart projects are still detected as Dart and the Dart SDK version number in the status bar (right) does not mention Flutter
-
pub get
andpub upgrade
packages have been replaced byflutter
commands in the command palette/pubspec.yaml
toolbar - The status bar shows when a device is connected and if multiple devices are connected you can click on it to select the one to use for launching/debugging
- You can launch apps on the selected device by pressing
F5
(note: the first time you do this, Code will ask what type of app - selectFlutter
which will openlaunch.json
and then hitF5
again to launch - Breakpoints are hit correctly and you can step with the debugger
- Other debugger features work correctly (stack traces shows, can be navigated, watched variables/locals etc. work)
- Pressing the debugger
Restart
button (alsoCtrl
+Shift
+F5
) causes a hot reload - Breakpoints work after hot-reloading
Mac
- Flutter projects are detected as flutter and the Dart SDK version number in the status bar (right) shows that it’s the Flutter version
- Standard Dart projects are still detected as Dart and the Dart SDK version number in the status bar (right) does not mention Flutter
-
pub get
andpub upgrade
packages have been replaced byflutter
commands in the command palette/pubspec.yaml
toolbar - The status bar shows when a device is connected and if multiple devices are connected you can click on it to select the one to use for launching/debugging
- You can launch apps on the selected device by pressing
F5
(note: the first time you do this, Code will ask what type of app - selectFlutter
which will openlaunch.json
and then hitF5
again to launch - Breakpoints are hit correctly and you can step with the debugger
- Other debugger features work correctly (stack traces shows, can be navigated, watched variables/locals etc. work)
- Pressing the debugger
Restart
button (alsoCtrl
+Shift
+F5
) causes a hot reload - Breakpoints work after hot-reloading
Linux
- Flutter projects are detected as flutter and the Dart SDK version number in the status bar (right) shows that it’s the Flutter version
- Standard Dart projects are still detected as Dart and the Dart SDK version number in the status bar (right) does not mention Flutter
-
pub get
andpub upgrade
packages have been replaced byflutter
commands in the command palette/pubspec.yaml
toolbar - The status bar shows when a device is connected and if multiple devices are connected you can click on it to select the one to use for launching/debugging
- You can launch apps on the selected device by pressing
F5
(note: the first time you do this, Code will ask what type of app - selectFlutter
which will openlaunch.json
and then hitF5
again to launch - Breakpoints are hit correctly and you can step with the debugger
- Other debugger features work correctly (stack traces shows, can be navigated, watched variables/locals etc. work)
- Pressing the debugger
Restart
button (alsoCtrl
+Shift
+F5
) causes a hot reload - Breakpoints work after hot-reloading
If you get stuck, feel free to give me a shout in Gitter Chat.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:7
- Comments:64 (55 by maintainers)
Top Results From Across the Web
How to release your Flutter app to App Center for beta testing
You get to release your application to targeted users to test and uncover bugs in your app — in other words, to beta...
Read more >Testing Flutter apps
Testing Flutter apps ... The more features your app has, the harder it is to test manually. Automated tests help ensure that your...
Read more >TestFairy for Flutter Apps | Mobile beta testing done right
TestFairy is a mobile quality platform that helps mobile teams automate your app distribution, streamline your development process, manage feedback cycles, and ...
Read more >Join the Flutter Store beta - TestFlight - Apple
To test beta versions of apps and App Clips using TestFlight, you'll need to accept an email or public link invitation from the...
Read more >Flutter Beta - Monday Hero
Flutter Beta · What's New? · You can easily convert Figma, Adobe XD and Sketch designs into Flutter code to build natively compiled...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Unfortunately I’ve hit another issue with debugging flutter apps. Breakpoints don’t seem to work after a hot reload (even after I’ve implemented what I understood to be required). I’ve raised https://github.com/flutter/flutter/issues/11040 hoping for some input; though it means it’s likely to be a little longer before this is ready to release (I’d hoped it’d be in a reasonable state this weekend, but it’s very unlikely now).
Once I managed to get to the bottom of these issues I’ll upload another beta for some final testing before it goes live. Thanks for all the testing so far!
I’ll try and give it another go on my Ubuntu setup tomorrow if I get chance. 😃