When using appium to automate a native Android application on a real device, there is an exception that occurs with the OpenQA.Selenium.WebDriverException saying: The HTTP request to the remote WebDriver server for URL timed out after 60 seconds.
Upon checking the Appium server logs, the following information was found:
info: Console LogLevel: debug
info: --> POST /wd/hub/session {"desiredCapabilities":{"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: Client User-Agent string: undefined info: [debug] The following desired capabilities were provided, but not recognized by Appium. They will be passed on to any other services running on this server. : device, platform info: [debug] Didn't get the app but did get the Android package, will attempt to launch it on the device info: [debug] Creating a new Appium session with ID 0762641e-991f-4b4b-8953-e4b9135f22ef info: Starting Android Appium info: [debug] Getting Java version info: Java version is: 1.8.0_45 info: [debug] Checking whether adb is present warn: The ANDROID_HOME environment variable is not set to the Android SDK root directory path. ANDROID_HOME is required for compatibility with SDK 23+. Checking along PATH for adb. info: [debug] executing cmd: where adb info: [debug] Using adb from G:\adb\sdk\platform-tools\adb.exe
warn: No app capability, can't parse package/activity info: [debug] Set chromedriver binary as: C:\Appium\Appium\node_modules\appium\build\chromedriver\windows\chromedriver.exe info: [debug] Using fast reset? true info: [debug] Preparing the device for the session info:[debug] Not checking whether the app is present since we are assuming it's already on the device info: Retrieving 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 device(s) connected info: Found device ID 43007015586711f1 info: [debug] Setting the device id to 43007015586711f1 info: [debug] Waiting for the device to be ready and to respond to shell commands (timeout = 5) info: [debug] executing 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] Starting logcat capture error: Logcat capture failed: spawn ENOENT info: [debug] Stopping logcat capture info: <-- POST /wd/hub/session - - ms - -
What could be causing this issue?