Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Steam removed" issue happens once "Handle Future Dialogs" is used more than once #3367

Open
amodzelewski opened this issue Jan 9, 2024 · 5 comments
Labels
bug Something isn't working priority: medium

Comments

@amodzelewski
Copy link

Describe the bug
If "Handle Future Dialogs" keyword is called more than once then then test fails and "Stream removed" error appears in the logs.

To Reproduce
Steps to reproduce the behavior:

  1. Open New Context
  2. Go to some page
  3. Use any reusable methotd that contains 'Handle Future Dialogs action=accept" inside
  4. Go to some other page within the same context
  5. Use any other reusable method that contains 'Handle Future Dialogs action=accept" inside

Code example:
The Test Causing The Error
[Documentation] This is just to report the problem
${case_id} Create Case
Open Case With Case Id case_id=${case_id}
Close This Case <-- this is reusable method that contains 'Hande Future Dialogs' inside
Go To Some Other Page
Delete Some Existing Report report_title=Report example <-- this is reusable method that contains 'Hande Future Dialogs' inside

Expected behavior
Test should pass and close the browser at the end.

Screenshots
2024-01-09_16h26_19

Desktop (please complete the following information):

  • OS: [Windows 10 Pro]
  • Browser [Chrome]
  • Version [120.0.6099.200]

Additional context
The idea that comes to my mind is to create additional keyword that will handle just one single alert.

@amodzelewski
Copy link
Author

Thre workaround is to close existing context and open a new one before the second 'Handle Future Dialogs' is called.

@aaltat
Copy link
Member

aaltat commented Jan 11, 2024

@allcontributors please add @amodzelewski for bugs

Copy link
Contributor

@aaltat

@amodzelewski already contributed before to bug

@aaltat aaltat added bug Something isn't working priority: medium labels Jan 11, 2024
@jeremy-of-laurel
Copy link

jeremy-of-laurel commented Feb 16, 2024

I have the same scenario issue on my end, except when I attempt to leave a dirty page and accept the alert, I get a Socket Closed error:
socket_closed

Ubuntu 22.04.3
Browser: Chrome
robotframework-browser 18.1.0

@aaltat
Copy link
Member

aaltat commented Oct 21, 2024

If you use https://marketsquare.github.io/robotframework-browser/Browser.html#Wait%20For%20Alerts keyword from 18.9.1 version. Do you still experience this problem?

Most likely this is caused same thing as with #3785

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority: medium
Projects
None yet
Development

No branches or pull requests

3 participants