Exception: Guarded function conflict error during tap in latest RC 3.0.0-rc.9

[amitkumar-qa]

@jonsamwell Getting error while taping on element in android ,
Below function gives error:
Future selectClientDetails(String contactName) async { await appDriver.tap(clientDropdown); }
In above function appDriver is object of AppDriverAdapter.

Error below:

I/flutter ( 7983): × Then User selects client "[test@test.com](mailto:test@test.com)" # :0 took 3ms I/flutter ( 7983): Exception: Guarded function conflict. I/flutter ( 7983): You must use "await" with all Future-returning test APIs. I/flutter ( 7983): The guarded method "pumpAndSettle" from class WidgetTester was called from package:flutter_gherkin/src/flutter/adapters/widget_tester_app_driver_adapter.dart on line 21. I/flutter ( 7983): Then, the "selectClientDetails" method from class InvoiceDetailsPage was called from file:///Users/ak/repo/integration_test/gherkin/steps/invoice_steps/invoice_details_page_steps.dart on line 10. I/flutter ( 7983): The first method (WidgetTester.pumpAndSettle) had not yet finished executing at the time that the second method (InvoiceDetailsPage.selectClientDetails) was called. Since both are guarded, and the second was not a nested call inside the first, the first must complete its execution before the second can be called. Typically, this is achieved by putting an "await" statement in front of the call to the first. I/flutter ( 7983): I/flutter ( 7983): When the first method (WidgetTester.

[jonsamwell]

@amitkumar-qa could you add your code here for that step. I can't see any unawaited calls to pumpAndSettle

[jonsamwell]

Actually I think this is solved by this PR #230

You could try that branch and see if you experience the same issue

[amitkumar-qa]

@jonsamwell Yes might be, leme try this branch

[jonsamwell]

@amitkumar-qa could you give this a go in the latest rc relesae 3.0.0-rc.10?

[amitkumar-qa]

@jonsamwell Sure , let me check

[jonsamwell]

Thanks

[WernerRaathAtPolymorph]

FYI If you create your own step file using the exact same code as for tap_widget_with_text_step.dart, rename all cases of tap to something like click and omit the await context.world.appDriver.waitForAppToSettle(); line, it actually succeeds.

I believe the issue here is with await context.world.appDriver.waitForAppToSettle();. @amitkumar-qa could you try this and see if it solves your issue?

[WernerRaathAtPolymorph]

I can confirm that this error happens before Scenarios as well. This issue is also intermittent. Could be a race condition?

[jonsamwell]

Should be fixed in Fixed in 3.0,0-rc-11

[amitkumar-qa]

Hi @jonsamwell This issue still persists in 3.0,0-rc-11 also , and its all about "context.world.appDriver.waitForAppToSettle()" , it might be because pumpandsettle is stuck if app page has infinite animation.
So @WernerRaathAtPolymorph solution mentioned above works where i need to omit waitForAppToSettle().
Thank you so much guys.
I encountered one more issue related to screenshot in 3.0,0-rc-11, have raised it separately-#235

[jonsamwell]

You should be able to set the configuration parameter ` waitImplicitlyAfterAction` to false to stop the implicit pump and settle actions.

…

On Fri, Jun 24, 2022, 6:00 PM amitkumar-qa ***@***.***> wrote: Hi @jonsamwell <https://github.com/jonsamwell> This issue still persists in 3.0,0-rc-11 also , and its all about "context.world.appDriver.waitForAppToSettle()" , it might be because pumpandsettle is stuck if app page has infinite animation. So @WernerRaathAtPolymorph <https://github.com/WernerRaathAtPolymorph> solution mentioned above works where i need to omit waitForAppToSettle(). Thank you so much guys. I encountered one more issue related to screenshot in 3.0,0-rc-11, have raised it separately-#235 <#235> — Reply to this email directly, view it on GitHub <#231 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4F7ILUTFPN5GJOWOXRGZLVQVTJTANCNFSM5ZH3USRA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[amitkumar-qa]

@jonsamwell I tried with waitImplicitlyAfterAction`=true.
Even after i am getting below error

══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════ The following assertion was thrown running a test: Guarded function conflict. You must use "await" with all Future-returning test APIs. The guarded method "pumpAndSettle" from class WidgetTester was called from package:flutter_gherkin/src/flutter/adapters/widget_tester_app_driver_adapter.dart on line 42. Then, it was called from package:flutter_gherkin/src/flutter/runners/gherkin_integration_test_runner.dart on line 530. The first method had not yet finished executing at the time that the second method was called. Since both are guarded, and the second was not a nested call inside the first, the first must complete its execution before the second can be called. Typically, this is achieved by putting an "await" statement in front of the call to the first.

[jonsamwell]

@amitkumar-qa try the new rc-15 release, I've removed the default frame binding policy as it was set to benchmarking which can not schedule all frames.

[amitkumar-qa]

@jonsamwell I will check and update you on this soon