VMServiceFlutterDriver: Flutter Driver extension is taking a long time to become available. Ensure your test app (often "lib/main.dart") imports "package:flutter_driver/driver_extension.dart" and calls enableFlutterDriverExtension() as the first call in main().```
Could you also please share your build’s URL link and enable Support Access? We’ll check it out and try to see what could be the reason behind this issue
I checked your build and wanted to ask if you could switch the custom script step to the Flutter Test step, but according to your workflow editor you’ve already made this change. Nevertheless, I haven’t seen any new builds with the updated workflow as of yet, can you let me know if there are any changes once there is?
So I didn’t quite understand your instructions. Our tests are failing in the “Flutter Driver” step, not the Flutter Test step.
In any case, we thought we moved past this by upgrading to Bitrise Elite plan but we started seeing issues again. Sometimes its the original VMServiceFlutterDriver problem but sometimes its just sporadic test failures that we can never reproduce locally.
It seems the issue is due to the emulator being created very slowly on this stack, but we could try multiple things to work around this.
The first is to use a script step, described in this article: Failed to boot emulator device (AVD) – Bitrise
Please note that the script there is written for an android API 29, but you merely need to switch it up with whichever you need (currently it is set to API 30 in your AVD Manager step).
For a number of other users what helped is to switch to an Ubuntu stack from an Xcode stack