Created
November 23, 2023 18:39
-
-
Save wazzeps/c76e8dbfb29786b4d65236fb50bfabbd to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[HTTP] --> POST /session/f25b32f8-72d6-45ba-8717-ead776ee4988/context | |
[HTTP] {"name":"WEBVIEW_chrome"} | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] Calling AppiumDriver.setContext() with args: ["WEBVIEW_chrome","f25b32f8-72d6-45ba-8717-ead776ee4988"] | |
[AppiumDriver@ed52] Clearing new command timeout pre-emptively since plugin(s) will handle this command | |
[AppiumDriver@ed52] Plugins which can handle cmd 'setContext': images | |
[AppiumDriver@ed52] Plugin images is now handling cmd 'setContext' | |
[AppiumDriver@ed52] Executing default handling behavior for command 'setContext' | |
[AndroidDriver] Getting a list of available webviews | |
[ADB] Running '/home/x/.repo/repository/com.google.androidsdk/androidsdk-26.1.1-r33-linux/platform-tools/adb -P 5037 -s emulator-5554 shell cat /proc/net/unix' | |
[AndroidDriver] Parsed 2 active devtools sockets: ["@chrome_devtools_remote","@webview_devtools_remote_11987"] | |
[AndroidDriver] Collecting CDP data of 2 webviews | |
[AndroidDriver] Forwarding remote port chrome_devtools_remote to a local port in range 10900..11000 | |
[AndroidDriver] You could use the 'webviewDevtoolsPort' capability to customize the starting port number | |
[AndroidDriver] Forwarding remote port webview_devtools_remote_11987 to a local port in range 10900..11000 | |
[AndroidDriver] You could use the 'webviewDevtoolsPort' capability to customize the starting port number | |
[ADB] Running '/home/x/.repo/repository/com.google.androidsdk/androidsdk-26.1.1-r33-linux/platform-tools/adb -P 5037 -s emulator-5554 forward tcp:10900 localabstract:chrome_devtools_remote' | |
[ADB] Removing forwarded port socket connection: 10900 | |
[ADB] Running '/home/x/.repo/repository/com.google.androidsdk/androidsdk-26.1.1-r33-linux/platform-tools/adb -P 5037 -s emulator-5554 forward --remove tcp:10900' | |
[ADB] Running '/home/x/.repo/repository/com.google.androidsdk/androidsdk-26.1.1-r33-linux/platform-tools/adb -P 5037 -s emulator-5554 forward tcp:10900 localabstract:webview_devtools_remote_11987' | |
[ADB] Removing forwarded port socket connection: 10900 | |
[ADB] Running '/home/x/.repo/repository/com.google.androidsdk/androidsdk-26.1.1-r33-linux/platform-tools/adb -P 5037 -s emulator-5554 forward --remove tcp:10900' | |
[AndroidDriver] CDP data collection completed | |
[AndroidDriver] WEBVIEW_11987 mapped to pid 11987 | |
[AndroidDriver] Getting process name for webview 'WEBVIEW_11987' | |
[ADB] Running '/home/x/.repo/repository/com.google.androidsdk/androidsdk-26.1.1-r33-linux/platform-tools/adb -P 5037 -s emulator-5554 shell ps -A' | |
[AndroidDriver] Got process name: 'android.beta' | |
[AndroidDriver] Found 2 webviews: ["WEBVIEW_chrome","WEBVIEW_android.beta"] | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] Available contexts: ["NATIVE_APP","WEBVIEW_chrome","WEBVIEW_android.beta"] | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] Connecting to chrome-backed webview context 'WEBVIEW_chrome' | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] Identified chromeAndroidPackage as 'com.android.chrome' for context 'WEBVIEW_chrome' by CDP | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] A port was not given, using random free port: 44517 | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] Passing web view details to the Chromedriver constructor: { | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] "info": { | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] "Android-Package": "com.android.chrome", | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] "Browser": "Chrome/95.0.4638.74", | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] "Protocol-Version": "1.3", | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] "User-Agent": "Mozilla/5.0 (Linux; Android 12; sdk_gphone64_x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.74 Mobile Safari/537.36", | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] "V8-Version": "9.5.172.25", | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] "WebKit-Version": "537.36 (@d873fb00e1c78cb31aff20a9b300d18cca0cc284)", | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] "webSocketDebuggerUrl": "ws://127.0.0.1:10900/devtools/browser" | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] }, | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] "process": { | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] "name": "chrome", | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] "id": null | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] } | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] } | |
[AndroidDriver] Precalculated Chromedriver capabilities: { | |
[AndroidDriver] "androidPackage": "com.android.chrome", | |
[AndroidDriver] "androidUseRunningApp": true, | |
[AndroidDriver] "androidDeviceSerial": "emulator-5554" | |
[AndroidDriver] } | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] Before starting chromedriver, androidPackage is 'com.android.chrome' | |
[Chromedriver@48c1] Changed state to 'starting' | |
[Chromedriver@48c1] Using the static Chromedriver->Chrome mapping | |
[Chromedriver@48c1] The most recent known Chrome version: 119.0.6045 | |
[Chromedriver@48c1] Found 2 executables in '/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux' | |
[Chromedriver@48c1] The following Chromedriver executables were found: | |
[Chromedriver@48c1] '/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver-linux64_v119.0.6045.105' (version '119.0.6045.105', minimum Chrome version '119.0.6045') | |
[Chromedriver@48c1] '/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver_linux64_v95.0.4638.69' (version '95.0.4638.69', minimum Chrome version '95.0.4638') | |
[Chromedriver@48c1] Browser version in the supplied details: Chrome/95.0.4638.74 | |
[Chromedriver@48c1] Found Chrome bundle 'undefined' version '95.0.4638' | |
[Chromedriver@48c1] Found 1 executable capable of automating Chrome '95.0.4638'. | |
[Chromedriver@48c1] Choosing the most recent, '/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver_linux64_v95.0.4638.69'. | |
[Chromedriver@48c1] If a specific version is required, specify it with the `chromedriverExecutable`desired capability. | |
[Chromedriver@48c1] Set chromedriver binary as: /home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver_linux64_v95.0.4638.69 | |
[Chromedriver@48c1] Killing any old chromedrivers, running: pkill -15 -f "/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver_linux64_v95.0.4638.69.*--port=44517" | |
[Chromedriver@48c1] No old chromedrivers seem to exist | |
[Chromedriver@48c1] Cleaning this device's adb forwarded port socket connections: emulator-5554 | |
[ADB] List forwarding ports | |
[ADB] Running '/home/x/.repo/repository/com.google.androidsdk/androidsdk-26.1.1-r33-linux/platform-tools/adb -P 5037 -s emulator-5554 forward --list' | |
[Chromedriver@48c1] Spawning chromedriver with: /home/s/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver_linux64_v95.0.4638.69 --port=44517 --adb-port=5037 --verbose | |
[Chromedriver@48c1] ChromeDriver version: '95.0.4638.69' | |
[Chromedriver@48c1] Matched '/status' to command name 'getStatus' | |
[Chromedriver@48c1] Proxying [GET /status] to [GET http://127.0.0.1:44517/status] with no body | |
[Chromedriver@48c1] Got response with status 200: {"value":{"build":{"version":"95.0.4638.69 (6a1600ed572fedecd573b6c2b90a22fe6392a410-refs/branch-heads/4638@{#984})"},"message":"ChromeDriver ready for new sessions.","os":{"arch":"x86_64","name":"Linux","version":"5.15.0-88-generic"},"ready":true}} | |
[Chromedriver@48c1] Starting W3C Chromedriver session with capabilities: { | |
[Chromedriver@48c1] "capabilities": { | |
[Chromedriver@48c1] "alwaysMatch": { | |
[Chromedriver@48c1] "goog:chromeOptions": { | |
[Chromedriver@48c1] "androidPackage": "com.android.chrome", | |
[Chromedriver@48c1] "androidUseRunningApp": true, | |
[Chromedriver@48c1] "androidDeviceSerial": "emulator-5554" | |
[Chromedriver@48c1] }, | |
[Chromedriver@48c1] "goog:loggingPrefs": { | |
[Chromedriver@48c1] "browser": "ALL" | |
[Chromedriver@48c1] } | |
[Chromedriver@48c1] } | |
[Chromedriver@48c1] } | |
[Chromedriver@48c1] } | |
[Chromedriver@48c1] Matched '/session' to command name 'createSession' | |
[Chromedriver@48c1] Proxying [POST /session] to [POST http://127.0.0.1:44517/session] with body: {"capabilities":{"alwaysMatch":{"goog:chromeOptions":{"androidPackage":"com.android.chrome","androidUseRunningApp":true,"androidDeviceSerial":"emulator-5554"},"goog:loggingPrefs":{"browser":"ALL"}}}} | |
[Chromedriver@48c1] Webview version: 'Chrome/95.0.4638.74' | |
[Chromedriver@48c1] AxiosError: timeout of 240000ms exceeded | |
[Chromedriver@48c1] at RedirectableRequest.handleRequestTimeout (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/@appium/base-driver/node_modules/axios/lib/adapters/http.js:630:16) | |
[Chromedriver@48c1] at RedirectableRequest.emit (node:events:512:28) | |
[Chromedriver@48c1] at Timeout.<anonymous> (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/follow-redirects/index.js:179:12) | |
[Chromedriver@48c1] at listOnTimeout (node:internal/timers:573:17) | |
[Chromedriver@48c1] at processTimers (node:internal/timers:514:7) | |
[Chromedriver@48c1] UnknownError: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to the remote server. Original error: timeout of 240000ms exceeded | |
[Chromedriver@48c1] at JWProxy.command (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/@appium/base-driver/lib/jsonwp-proxy/proxy.js:355:13) | |
[Chromedriver@48c1] at runNextTicks (node:internal/process/task_queues:60:5) | |
[Chromedriver@48c1] at listOnTimeout (node:internal/timers:540:9) | |
[Chromedriver@48c1] at processTimers (node:internal/timers:514:7) | |
[Chromedriver@48c1] at Chromedriver.startSession (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/lib/chromedriver.js:742:5) | |
[Chromedriver@48c1] at Chromedriver.start (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/lib/chromedriver.js:667:7) | |
[Chromedriver@48c1] at AndroidUiautomator2Driver.setupNewChromedriver (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver/lib/commands/context.js:494:5) | |
[Chromedriver@48c1] at AndroidUiautomator2Driver.startChromedriverProxy (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver/lib/commands/context.js:216:12) | |
[Chromedriver@48c1] at AndroidUiautomator2Driver.switchContext (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver/lib/commands/context.js:107:7) | |
[Chromedriver@48c1] at AndroidUiautomator2Driver.setContext (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver/lib/commands/context.js:80:5) | |
[Chromedriver@48c1] Chromedriver exited unexpectedly with code null, signal SIGTERM | |
[Chromedriver@48c1] Changed state to 'stopped' | |
[Chromedriver@48c1] An unknown server-side error occurred while processing the command. Original error: Could not proxy command to the remote server. Original error: timeout of 240000ms exceeded | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] Encountered internal error running command: Error: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to the remote server. Original error: timeout of 240000ms exceeded | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] at Object.wrappedLogger.errorAndThrow (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/@appium/support/lib/logging.js:115:34) | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] at Chromedriver.start (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/lib/chromedriver.js:695:16) | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] at AndroidUiautomator2Driver.setupNewChromedriver (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver/lib/commands/context.js:494:5) | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] at AndroidUiautomator2Driver.startChromedriverProxy (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver/lib/commands/context.js:216:12) | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] at AndroidUiautomator2Driver.switchContext (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver/lib/commands/context.js:107:7) | |
[AndroidUiautomator2Driver@2d3a (f25b32f8)] at AndroidUiautomator2Driver.setContext (/home/x/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver/lib/commands/context.js:80:5) | |
[HTTP] <-- POST /session/f25b32f8-72d6-45ba-8717-ead776ee4988/context 500 240409 ms - 906 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment