[GH-ISSUE #41] errors when switching to webview context on higher than 6.0 #32

New issue

Closed

opened 2026-03-01 15:39:32 +03:00 by kerem · 4 comments

kerem commented

2026-03-01 15:39:32 +03:00

Owner

Originally created by @JohannesMerz on GitHub (Oct 11, 2017).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/41

When switching context to a embedded webview the installed chrome version is not sufficient for newer versions. Works with 5.1.1 but not with 6.x nor 7.x

Error: [context("WEBVIEW_com.eyesquare.sdktest")] 
  Error response status: 13, UnknownError - An unknown server-side error occurred while processing the command. 
  Selenium error: An unknown server-side error occurred while processing the command. 
  Original error: unknown error: 
    Chrome version must be >= 53.0.2785.0
  (Driver info: chromedriver=2.26.436382 (70eb799287ce4c2208441fc057053a5b07ceabac),platform=Linux 3.16.0-4-amd64 x86_64)

This is my code for reference. Starting the app and getting the web views works. Just setting the context wont.

const wd = require('wd');

const driver = wd.promiseChainRemote("dev.eye-square.com", 4723);

driver.init({
  'browserName' : '',
  // 'version' : '7.1.1',
  'platformName': 'Android',
  'deviceName' : 'Samsung Galaxy S6',
  'app' : '/root/tmp/test-app.apk',
})
.sessions(log)
.contexts(log)
.context("WEBVIEW_xxx")
.fin(() => driver.quit())
.done()


function log (err, handles) {
  console.log(err, handles);
}

Additional info: It may be due to the emulator being out of date as thats in the logs when hitting

docker exec -it android-container tail -f /var/log/supervisor/docker-android.stdout.log

emulator: Listening for console connections on port: 5554
emulator: Serial number of this emulator (for ADB): emulator-5554
Your emulator is out of date, please update by launching Android Studio:
 - Start Android Studio
 - Select menu "Tools > Android > SDK Manager"
 - Click "SDK Tools" tab
 - Check "Android SDK Tools" checkbox
 - Click "OK"

Originally created by @JohannesMerz on GitHub (Oct 11, 2017). Original GitHub issue: https://github.com/budtmo/docker-android/issues/41 When switching context to a embedded webview the installed chrome version is not sufficient for newer versions. Works with 5.1.1 but not with 6.x nor 7.x ``` Error: [context("WEBVIEW_com.eyesquare.sdktest")] Error response status: 13, UnknownError - An unknown server-side error occurred while processing the command. Selenium error: An unknown server-side error occurred while processing the command. Original error: unknown error: Chrome version must be >= 53.0.2785.0 (Driver info: chromedriver=2.26.436382 (70eb799287ce4c2208441fc057053a5b07ceabac),platform=Linux 3.16.0-4-amd64 x86_64) ``` This is my code for reference. Starting the app and getting the web views works. Just setting the context wont. ``` const wd = require('wd'); const driver = wd.promiseChainRemote("dev.eye-square.com", 4723); driver.init({ 'browserName' : '', // 'version' : '7.1.1', 'platformName': 'Android', 'deviceName' : 'Samsung Galaxy S6', 'app' : '/root/tmp/test-app.apk', }) .sessions(log) .contexts(log) .context("WEBVIEW_xxx") .fin(() => driver.quit()) .done() function log (err, handles) { console.log(err, handles); } ``` Additional info: It may be due to the emulator being out of date as thats in the logs when hitting ` docker exec -it android-container tail -f /var/log/supervisor/docker-android.stdout.log` ``` emulator: Listening for console connections on port: 5554 emulator: Serial number of this emulator (for ADB): emulator-5554 Your emulator is out of date, please update by launching Android Studio: - Start Android Studio - Select menu "Tools > Android > SDK Manager" - Click "SDK Tools" tab - Check "Android SDK Tools" checkbox - Click "OK" ```

kerem closed this issue

2026-03-01 15:39:32 +03:00

kerem commented

2026-03-01 15:39:33 +03:00

Author

Owner

@budtmo commented on GitHub (Nov 22, 2017):

Hi @JohannesMerz ,

Could you try it again with the new release if the bug is still there?

@budtmo commented on GitHub (Nov 22, 2017): Hi @JohannesMerz , Could you try it again with the new release if the bug is still there?

kerem commented

2026-03-01 15:39:33 +03:00

Author

Owner

@JohannesMerz commented on GitHub (Nov 22, 2017):

i wont have time for this this week unfortunatly, hopefully next week

@JohannesMerz commented on GitHub (Nov 22, 2017): i wont have time for this this week unfortunatly, hopefully next week

kerem commented

2026-03-01 15:39:33 +03:00

Author

Owner

@budtmo commented on GitHub (Jan 3, 2018):

I will close this issue because there is no response. Please feel free to reopen the issue if the bug is still there.

@budtmo commented on GitHub (Jan 3, 2018): I will close this issue because there is no response. Please feel free to reopen the issue if the bug is still there.

kerem commented

2026-03-01 15:39:33 +03:00

Author

Owner

@eyal919 commented on GitHub (Aug 28, 2019):

did someone solved it?

@eyal919 commented on GitHub (Aug 28, 2019): did someone solved it?