Closed vdelendik closed 5 months ago
reproduced the connection to the appium via the emulator with the erroneous capability adbExecTimeout=90000[
without agents
when appium sees an incorrect capability, it forwards [HTTP] <-- POST /session 500
and does not allow a new session to be created and throws an error in the form
[AppiumDriver@b587] Encountered internal error running command: Error:
in this case adds details
'adbExecTimeout' must be of type number
full log
[AppiumDriver@b587] Calling AppiumDriver.createSession() with args: [{"app":"/Users/vadimbabaiev/Downloads/carinademoexample.apk","adbExecTimeout":"90000[","platformVersion":"14.0","automationName":"UiAutomator2","platformName":"Android","deviceName":"Pixel 4 API 34"},null,{"firstMatch":[{"appium:adbExecTimeout":"90000[","appium:app":"/Users/vadimbabaiev/Downloads/carinademoexample.apk","appium:automationName":"UiAutomator2","appium:deviceName":"Pixel 4 API 34","platformName":"android","appium:platformVersion":"14.0"}]}]
[AppiumDriver@b587] Event 'newSessionRequested' logged at 1709215917515 (15:11:57 GMT+0100 (Central European Standard Time))
[Appium] Attempting to find matching driver for automationName 'UiAutomator2' and platformName 'android'
[Appium] The 'uiautomator2' driver was installed and matched caps.
[Appium] Will require it at /Users/vadimbabaiev/.appium/node_modules/appium-uiautomator2-driver
[Appium] Requiring driver at /Users/vadimbabaiev/.appium/node_modules/appium-uiautomator2-driver/build/index.js
[AppiumDriver@b587] Appium v2.4.1 creating new AndroidUiautomator2Driver (v2.44.0) session
[AppiumDriver@b587] Checking BaseDriver versions for Appium and AndroidUiautomator2Driver
[AppiumDriver@b587] Appium's BaseDriver version is 9.5.0
[AppiumDriver@b587] AndroidUiautomator2Driver's BaseDriver version is 9.5.0
[AndroidUiautomator2Driver@4564] Creating session with W3C capabilities: {
[AndroidUiautomator2Driver@4564] "alwaysMatch": {
[AndroidUiautomator2Driver@4564] "platformName": "android",
[AndroidUiautomator2Driver@4564] "appium:adbExecTimeout": "90000[",
[AndroidUiautomator2Driver@4564] "appium:app": "/Users/vadimbabaiev/Downloads/carinademoexample.apk",
[AndroidUiautomator2Driver@4564] "appium:automationName": "UiAutomator2",
[AndroidUiautomator2Driver@4564] "appium:deviceName": "Pixel 4 API 34",
[AndroidUiautomator2Driver@4564] "appium:platformVersion": "14.0"
[AndroidUiautomator2Driver@4564] },
[AndroidUiautomator2Driver@4564] "firstMatch": [
[AndroidUiautomator2Driver@4564] {}
[AndroidUiautomator2Driver@4564] ]
[AndroidUiautomator2Driver@4564] }
[AndroidUiautomator2Driver@4564] Deleting UiAutomator2 session
[AndroidUiautomator2Driver@4564] Unable to stop ChromeDriver proxies: Cannot read properties of undefined (reading 'proxyReqRes')
[AppiumDriver@b587] Event 'newSessionStarted' logged at 1709215917530 (15:11:57 GMT+0100 (Central European Standard Time))
[AppiumDriver@b587] Encountered internal error running command: SessionNotCreatedError: A new session could not be created. Details: 'adbExecTimeout' must be of type number
[AppiumDriver@b587] at AndroidUiautomator2Driver.createSession (/usr/local/lib/node_modules/appium/node_modules/@appium/base-driver/lib/basedriver/driver.ts:272:13)
[AppiumDriver@b587] at AndroidUiautomator2Driver.createSession (/Users/vadimbabaiev/.appium/node_modules/appium-uiautomator2-driver/lib/driver.ts:346:75)
[AppiumDriver@b587] at AppiumDriver.createSession (/usr/local/lib/node_modules/appium/lib/appium.js:717:56)
[HTTP] <-- POST /session 500 18 ms - 644
[HTTP]
closing as won't fix. backend appium logs contains exact reason:
[AppiumDriver@b587] Encountered internal error running command: SessionNotCreatedError: A new session could not be created. Details: 'adbExecTimeout' must be of type number
so user can read and identify root cause.
after providing mistakenly
capabilities.adbExecTimeout=90000[
capability with square bracket session can't be started.... but the problem is that our reporting agent crash test execution earlier:potentially RetryUtils in reporting agent might be a reason. let's first of all repro on dev env and debug...