Appium timeout error while connecting to driver
I am using appium to automate a native Android app on a real device, but I get the following exception in OpenQA.Selenium.WebDriverException HTTP request to remote WebDriver server for URL http://127.0.0.1:4723/wd/hub/session expires after 60 seconds.
When checking the appium server, the mentioned logs look like this:
info: Console LogLevel: debug
info: → POST / wd / hub / session {"wishCapabilities": {"device": "Android", "platform": "Windows", "deviceName": "Soti India (SM-P600)", "platformName": "Android", "platformVersion": "4,4", "appPackage": "net.soti.hub", "appActivity": "net.soti.securecontentlibrary.activities.SplashActivity"}} info: string User User Agent: undefinedinfo: [debug] The following desired features were provided, but were not recognized by appium. They will be passed to other services running on this server .: device, platform info: [debug] Didn't receive the application, but got the Android package, will try to run it on the device info:[debug] Create new session appium 0762641e-991f-4b4b-8953-e4b9135f22ef info: Start android appium info: [debug] Get Java version info: Java version: 1.8.0_45 info: [debug] Check for adb warn: environment variable ANDROID_HOME not installed to Android SDK root directory. ANDROID_HOME is required for SDK 23+ compatibility. Checking by PATH for adb. info: [debug] Executing cmd: where adb info: [debug] Using adb from G: \ adb \ sdk \ platform-tools \ adb.exe[debug] Using adb from G: \ adb \ sdk \ platform-tools \ adb.exe[debug] Using adb from G: \ adb \ sdk \ platform-tools \ adb.exe
warn: no application capability, cannot parse package / activity info: [debug] Install chronograph binary as: C: \ Appium \ Appium \ node_modules \ appium \ build \ chromedriver \ windows \ chromedriver.exe info: [debug] Using quick reset ? true info: [debug] Preparing the device for the session info: [debug] Doesn't check if the application is present since we are already accepting it on the device info: Removing the device info: [debug] Trying to find a connected Android device info: [debug] Getting connected devices ... info: [debug] Executing cmd: "G: \ adb \ sdk \ platform-tools \ adb.exe" devices info: [debug] 1 info device connected: device found 43007015586711f1 info: [debug] Setting device ID to 43007015586711f1 info:[debug] Wait for the device to be ready and respond to shell commands (timeout = 5) info: [debug] Execute cmd: "G: \ adb \ sdk \ platform-tools \ adb.exe" -s 43007015586711f1 wait-for-device info: [debug] Executing cmd: "G: \ adb \ sdk \ platform-tools \ adb.exe" -s 43007015586711f1 shell "echo 'ready'" info: [debug] Start logcat capture Error: logcat capture failed: spawn ENOENT info : [debug] Stop capturing logcat info: <- POST / wd / hub / session - - ms - -spawn ENOENT info: [debug] Stop capturing logcat info: <- POST / wd / hub / session - - ms - -spawn ENOENT info: [debug] Stop capturing logcat info: <- POST / wd / hub / session - - ms - -
What a possible problem
source to share
It seems you haven't configured the android sdk path in your appium gui ..
In your appium gui under android setting you have to set android sdk path
if you are using appium from the console then you probably need to set ANDROID_HOME to environment variables and assign your environment path to it.
source to share