Appium fails when trying to interact with Android. This happens some of the time. Below is an example where it fails to install. This also happens when trying to clear Logcat. Any idea what’s going on? The same behavior is exhibited. Attemps to interact with Android and 10 minutes later a new session is created.
Console LogLevel: debug
[37m-->[39m [37mPOST[39m [37m/wd/hub/session[39m [90m{"desiredCapabilities":{...}}
Client User-Agent string: Apache-HttpClient/4.3.4 (java 1.5)
[debug] No appActivity desired capability or server param. Parsing from apk.
[debug] No appPackage desired capability or server param. Parsing from apk.
[debug] Using local app from desired caps: test.apk
[debug] Creating new appium session 92680fcf-890b-422f-a408-82358e5dae0e
Starting android appium
[debug] Getting Java version
Java version is: 1.8.0_45
[debug] Checking whether adb is present
[debug] Using adb from adb
[debug] Parsing package and activity from app manifest
[debug] Checking whether aapt is present
[debug] Using aapt from aapt
[debug] Extracting package and launch activity from manifest.
[debug] executing cmd: aapt dump badging test.apk
[debug] badging package: com.test.beta
[debug] badging act: com.test.beta
[debug] Parsed package and activity are: com.test.beta/com.test.beta
[debug] Using fast reset? true
[debug] Preparing device for session
[debug] Checking whether app is actually present
Retrieving device
[debug] Trying to find a connected android device
[debug] Getting connected devices...
[debug] executing cmd: adb devices
[debug] 4 device(s) connected
Found device d
[debug] Setting device id to d
[debug] Waiting for device to be ready and to respond to shell commands (timeout = 5)
[debug] executing cmd: adb -s d wait-for-device
[debug] executing cmd: adb -s d shell "echo 'ready'"
[debug] Starting logcat capture
[37m<-- POST /wd/hub/session [39m[32m-[39m[90m - ms - -[39m [90m[39m
[37m-->[39m [37mPOST[39m [37m/wd/hub/session[39m [90m{"desiredCapabilities":{...}}[39m
Client User-Agent string: Apache-HttpClient/4.3.4 (java 1.5)
Found an existing session to clobber, shutting it down first...
Shutting down appium session