The 'flutter:waitFor' command doesn't work with '{durationMilliseconds: 100}' option

First case Using the flutter:waitFor command with {durationMilliseconds: 100} as specified in the appium-flutter-driver Commands returns an error:

 An unknown server-side error occurred while processing the command. Original error: durationMilliseconds is not a valid options.

Command example:

await driver.execute('flutter:waitFor', find.byValueKey('password'), {durationMilliseconds: 100});

Second case If use the flutter:waitFor command with milliseconds as mentioned in one of the ‘Issues’ here, for example:

await driver.execute('flutter:waitFor', find.byValueKey('password'), 5000);

It works, the command waits for 5 seconds (with 3 tries, 15 seconds in total), BUT in case the element is not displayed within the specified time - it also returns an server-side error:

 An unknown server-side error occurred while processing the command. Original error: Cannot execute command waitFor, server reponse {
  "isError": true,
  "response": "Timeout while executing waitFor: TimeoutException after 0:00:05.000000: Future not completed\n",
  "type": "_extensionType",
  "method": "ext.flutter.driver"
}

I’m using WebdriverIO + appium 2.0.0-beta.44 + appium-flutter-driver 1.7.2 + appium-flutter-finder 0.1.0

So what is the correct way to use the flutter:waitFor command? Maybe there is some other alternative?

[KazuCocoa]

The error and the behavior itself come from Flutter/Dart VM. Appium flutter driver just sends commands defined in https://api.flutter.dev/flutter/flutter_driver/flutter_driver-library.html to them. Thus, if something behavior seems weird, maybe you need to report it in the Flutter team. (but I guess they won’t maintain the flutter_driver so much.)

[KazuCocoa]

Thank you. I’ve modified the readme