Running flutter emulators includes bogus entries that are caused by errors that show up in the output of emulator -list-avds (an Android SDK tool which Flutter parses).
√ ags % flutter emulators
3 available emulators:
apple_ios_simulator • iOS Simulator
• Apple • ios
INFO | Storing crashdata in: /tmp/android-rhisiart/emu-crash-34.1.19.db, detection is enabled for process: 88721 • INFO | Storing crashdata in:
/tmp/android-rhisiart/emu-crash-34.1.19.db, detection is enabled for process: 88721 • • android
Pixel_8_Pro_API_33 • Pixel 8 Pro API 33
• Google • android
To run an emulator, run 'flutter emulators --launch <emulator id>'.
To create a new emulator, run 'flutter emulators --create [--name xyz]'.
Running the underlying SDK command manually shows the same messages in the output:
√ ~ % /Users/rhisiart/Library/android/sdk/emulator/emulator -list-avds
INFO | Storing crashdata in: /tmp/android-rhisiart/emu-crash-34.1.19.db, detection is enabled for process: 95538
WARNING | Crash annotation is very large (16415), only 16384 bytes will be recorded, 31 bytes are lost.
Pixel_8_Pro_API_33
Running the "old" version of emulator from the tools folder does not include this output:
√ ~ % /Users/rhisiart/Library/android/sdk/tools/emulator -list-avds
Pixel_8_Pro_API_33
Having discussed the matter with @DanTup, he suggested that I raise the issue against this repo.
For the full thread, please see Dart-Code/Dart-Code#5052
Running
flutter emulatorsincludes bogus entries that are caused by errors that show up in the output ofemulator -list-avds(an Android SDK tool which Flutter parses).Running the underlying SDK command manually shows the same messages in the output:
Running the "old" version of
emulatorfrom thetoolsfolder does not include this output:√ ~ % /Users/rhisiart/Library/android/sdk/tools/emulator -list-avds Pixel_8_Pro_API_33Having discussed the matter with @DanTup, he suggested that I raise the issue against this repo.
For the full thread, please see Dart-Code/Dart-Code#5052