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

terminateApp() closes chromedriver connection #707

Open
studioromeo opened this issue Jan 2, 2024 · 1 comment
Open

terminateApp() closes chromedriver connection #707

studioromeo opened this issue Jan 2, 2024 · 1 comment

Comments

@studioromeo
Copy link

Hey!

When using terminateApp it seems to close the chromedriver connection and doesn't reconnect when using activateApp.

This means when using findElement after terminateApp the request fails with a 500 error unknown error: An unknown server-side error occurred while processing the command. Original error: disconnected: not connected to DevTools

This didn't happen with the deprecated closeApp method, I assume because the session was never destroyed.

I've created an example repo https://github.com/studioromeo/bug-webdriver-chromedriver which demonstrates the issue. It uses webdriver but the appium logs seem to suggest its at the driver level

Let me know if I can help further or where I should look to investigate a fix 👍

@mykola-mokhnach
Copy link
Contributor

It was always working like that. You need to quit the driver and start a new session if you want to reproduce the legacy behaviour. Handling chromedriver restart together with app restart would be a new feature request (and I don't think might be picked up soon)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants