-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Error "chrome not reachable" when restarting android app with webview #459
Comments
Could you attach the appium log (and maybe logcat as well?)? a note: the message is chromedriver. https://github.com/bayandin/chromedriver/search?utf8=%E2%9C%93&q=chrome+not+reachable&type= |
Sorry for my delayed answer. I missed the message and then I worked on sth else for a while. I checked it again today and I have a different error but I am still not sure how to fix it. My current setup: "appium": "^1.14.1", Please find appium log below. If you need logcat as well I have it and can add it any time. "�[35m[HTTP]�[39m �[37m-->�[39m �[37mPOST�[39m �[37m/wd/hub/session�[39m |
The error message is pretty clear as for my taste |
I did it but I still get the other error after restarting android app:
|
Could you attach the latest full server log? |
@KazuCocoa please find the log below:
|
3 similar comments
@KazuCocoa please find the log below:
|
@KazuCocoa please find the log below:
|
@KazuCocoa please find the log below:
|
You called From next version, launch/close will raise errors: https://github.com/appium/appium-espresso-driver/pull/485/files Then, I assume it should work |
@KazuCocoa I tried closeApp/terminateApp/reset(only reset seems to work) to stop the app and then startActivity to launch it. However, after restarting the app I still cannot get it running:
and:
|
It looks |
@KazuCocoa so which commands can I actually use to stop & start app on Android? WebdriverIO that we use have no |
According to http://appium.io/docs/en/commands/session/delete/, |
Well I think this documentation is not up to date as there is no endSession() method for webdriverio. Hence I am really confused as it seems there is not way to handle it when using webdriverio |
I think it's |
@jlipps I tried it yesterday as well but it deletes the session completely and I would have to start a new one providing all the capabilities etc. I cannot simply use startActivity afterwards as it complains that |
I tried to use |
Could you share the latest appium log?
Yes. |
�[35m[HTTP]�[39m �[37m-->�[39m �[37mPOST�[39m �[37m/wd/hub/session�[39m |
You sent below item.
But:
I quoted them from the top of your attached log. |
@KazuCocoa I fixed the capabilities and got rid of the error but now I have another one: capabilities:
the logs with new error (I tried appWaitActivity, appWaitPackage, appWaitDuration and no change):
|
mm, Not sure the cause, but does it happen on emulator, too?
|
@KazuCocoa I tried it on real device only, and this is how I need to execute the tests... |
I tried on a real device I had. It worked well. Android 9, Nokia device. Chromedriver was 76 supported one. If it was chromedriver related issue, you can try other chromedriver versions which support your chrome version. I think you should make sure the cause is your devices, env or other materials. |
@KazuCocoa so I got it working finally but only with "reloadSession". Nothing else worked. However, I have plenty of other issues now - bug reports, no test execution report generated, random failures. It's really flaky. I will open the separate issues for that. Thanks for help |
"appium": "^1.14.0-beta.1",
"appium-chromedriver": "^4.11.1",
Android Debug Bridge version 1.0.41
MacOS Mojave 10.14.5
Tested on Samsung Galaxy S2 & LG-H930
After #314 was closed as fixed I checked again the restarting of the android app and now I get a different error:
"An unknown server-side error occurred while processing the command. Original error: chrome not reachable"
I use:
automationName: "Espresso",
autoWebview: true,
and everything works fine after I start the app for the first time but fails after I resetApp with http://appium.io/docs/en/commands/device/app/reset-app/
The text was updated successfully, but these errors were encountered: