Problem with GoogleSignInOptions testing on Android

Hi, recently to app i’m testing development team added option to sign in with google account. Everything would be fine if only i could change my context to the new window. It didnt look like it’s opening in chrome or any other browser, but with my glorious debugging skills i’ve found out that its a “WEBVIEW_com.google.android.gms.ui”, so basically it is a chrome 😮 When im trying to change driver.context to that im getting this:

io.appium.java_client.NoSuchContextException: An unknown server-side error occurred while processing the command. Original error: Failed to start Chromedriver session: An unknown server-side error occurred while processing the command. Original error: unknown error: Failed to get sockets matching: @webview_devtools_remote_.*16137
  (make sure the app has its WebView configured for debugging)

In appium i got this:

[debug] [MJSONWP] Matched JSONWP error code 13 to UnknownError
[Chromedriver] Error: Failed to start Chromedriver session: An unknown server-side error occurred while processing the command. Original error: unknown error: Failed to get sockets matching: @webview_devtools_remote_.*16137
[Chromedriver]   (make sure the app has its WebView configured for debugging)
[Chromedriver]   (Driver info: chromedriver=2.44.609551 (5d576e9a44fe4c5b6a07e568f1ebc753f1214634),platform=Linux 5.1.14-121.current x86_64)
[Chromedriver]     at Object.wrappedLogger.errorAndThrow (/home/stanislaw/.npm-global/lib/node_modules/appium/node_modules/appium-support/lib/logging.js:78:13)
[Chromedriver]     at errorAndThrow (/home/stanislaw/.npm-global/lib/node_modules/appium/node_modules/appium-chromedriver/lib/chromedriver.js:560:13)
[debug] [WD Proxy] Matched '/session' to command name 'createSession'
[debug] [WD Proxy] Proxying [POST /session] to [POST http://127.0.0.1:8000/wd/hub/session] with body: {"desiredCapabilities":{"chromeOptions":{"androidPackage":"com.mayeryn.vendingmachine","androidUseRunningApp":true,"androidDeviceSerial":"emulator-5554"},"loggingPrefs":{"browser":"ALL"}}}
[debug] [WD Proxy] Got response with status 200: {"sessionId":"558aac7f07862bf7c7da4de453ae1f1e","status":13,"value":{"message":"unknown error: Failed to get sockets matching: @webview_devtools_remote_.*16137\n  (make sure the app has its WebView configured for debugging)\n  (Driver info: chromedriver=2.44.609551 (5d576e9a44fe4c5b6a07e568f1ebc753f1214634),platform=Linux 5.1.14-121.current x86_64)"}}
[WD Proxy] Got an unexpected response: {"sessionId":"558aac7f07862bf7c7da4de453ae1f1e","status":13,"value":{"message":"unknown error: Failed to get sockets matching: @webview_devtools_remote_.*16137\n  (make sure the app has its WebView configured for debugging)\n  (Driver info: chromedriver=2.44.609551 (5d576e9a44fe4c5b6a07e568f1ebc753f1214634),platform=Linux 5.1.14-121.current x86_64)"}}
[debug] [MJSONWP] Matched JSONWP error code 13 to UnknownError
[Chromedriver] Error: Failed to start Chromedriver session: An unknown server-side error occurred while processing the command. Original error: unknown error: Failed to get sockets matching: @webview_devtools_remote_.*16137
[Chromedriver]   (make sure the app has its WebView configured for debugging)
[Chromedriver]   (Driver info: chromedriver=2.44.609551 (5d576e9a44fe4c5b6a07e568f1ebc753f1214634),platform=Linux 5.1.14-121.current x86_64)
[Chromedriver]     at Object.wrappedLogger.errorAndThrow (/home/stanislaw/.npm-global/lib/node_modules/appium/node_modules/appium-support/lib/logging.js:78:13)
[Chromedriver]     at errorAndThrow (/home/stanislaw/.npm-global/lib/node_modules/appium/node_modules/appium-chromedriver/lib/chromedriver.js:560:13)
[Chromedriver] Chromedriver exited unexpectedly with code null, signal SIGTERM
[debug] [Chromedriver] Changed state to 'stopped'
[Chromedriver] Error: Failed to start Chromedriver session: An unknown server-side error occurred while processing the command. Original error: unknown error: Failed to get sockets matching: @webview_devtools_remote_.*16137
[Chromedriver]   (make sure the app has its WebView configured for debugging)
[Chromedriver]   (Driver info: chromedriver=2.44.609551 (5d576e9a44fe4c5b6a07e568f1ebc753f1214634),platform=Linux 5.1.14-121.current x86_64)
[Chromedriver]     at Object.wrappedLogger.errorAndThrow (/home/stanislaw/.npm-global/lib/node_modules/appium/node_modules/appium-support/lib/logging.js:78:13)
[Chromedriver]     at Chromedriver.errorAndThrow [as start] (/home/stanislaw/.npm-global/lib/node_modules/appium/node_modules/appium-chromedriver/lib/chromedriver.js:508:11)
[debug] [W3C (5af173ac)] Encountered internal error running command: Error: Failed to start Chromedriver session: An unknown server-side error occurred while processing the command. Original error: unknown error: Failed to get sockets matching: @webview_devtools_remote_.*16137
[debug] [W3C (5af173ac)]   (make sure the app has its WebView configured for debugging)
[debug] [W3C (5af173ac)]   (Driver info: chromedriver=2.44.609551 (5d576e9a44fe4c5b6a07e568f1ebc753f1214634),platform=Linux 5.1.14-121.current x86_64)
[debug] [W3C (5af173ac)]     at Object.wrappedLogger.errorAndThrow (/home/stanislaw/.npm-global/lib/node_modules/appium/node_modules/appium-support/lib/logging.js:78:13)
[debug] [W3C (5af173ac)]     at Chromedriver.errorAndThrow [as start] (/home/stanislaw/.npm-global/lib/node_modules/appium/node_modules/appium-chromedriver/lib/chromedriver.js:508:11)
[HTTP] <-- POST /wd/hub/session/5af173ac-3c52-457d-bd95-154d8c239b47/context 500 1490 ms - 1315
[HTTP] 
[HTTP] --> DELETE /wd/hub/session/5af173ac-3c52-457d-bd95-154d8c239b47

Im running tests on current appium beta (it was the same on other versions)

[mykola-mokhnach]

I don’t know how to fix it and don’t even know whether this is a third-party issue or something, that could be addressed on Appium side. If your company really wants the problem to be resolved ASAP then I would recommend hiring a consultant, who has appropriate skills there.

[mykola-mokhnach]

Closed as third party issue