I was not able to get the NATIVE App running with emulator Android 4.4.2 chrome version 37.0.2062.103 m, please check the below log, thanks in advance for your help.
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. : platform, acceptSslCerts, networkConnectionEnabled, version, databaseEnabled, app-package, deviceType, webStorageEnabled, device, app-wait-activity, app-activity
info: [debug] No appActivity desired capability or server param. Parsing from apk.
info: [debug] No appPackage desired capability or server param. Parsing from apk.
info: [debug] Using local app from desired caps: C:\sdk\build-tools\android-4.4.2\androidTEST.apk
info: [debug] Creating new appium session e857ae69-2651-4665-96a1-406e2e02e515
info: Starting android appium
info: [debug] Using fast reset? true
info: [debug] Preparing device for session
info: [debug] Checking whether app is actually present
info: [debug] Checking whether adb is present
info: [debug] Using adb from C:\sdk\platform-tools\adb.exe
info: Retrieving device
info: [debug] Trying to find a connected android device
info: [debug] Getting connected devices…
info: [debug] executing: “C:sdk\platform-tools\adb.exe” devices
info: [debug] 1 device(s) connected
info: Found device emulator-5554
info: [debug] Setting device id to emulator-5554
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 5)
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 wait-for-device
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “echo’ready’”
info: [debug] Starting logcat capture
info: [debug] Parsing package and activity from app manifest
info: [debug] Checking whether aapt is present
info: [debug] Using aapt from C:\sdk\build-tools\android-4.4.2\aapt.exe
info: [debug] packageAndLaunchActivityFromManifest: “C:\sdk\build-tools\android-4.4.2\aapt.exe” dump badging C:\sdk\build-tools\android-4.4.2\androidTEST.apk
info: [debug] badging package: com.home.simple
info: [debug] badging act: com.able.avm.dyna.dynaSplActivity
info: [debug] Parsed package and activity are: com.home.simple/com.able.avm.dyna.dynaSplActivity
info: [debug] Getting device API level
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “getpr
op ro.build.version.sdk”
info: [debug] Device is at API Level 19
info: Device API level is: 19
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “getpr
op persist.sys.language”
info: [debug] Current device language: en
info: [debug] java -jar “C:\Program Files\nodejs\node_modules\appium\node_modules\appium-adb\jars\appium_apk_tools.jar” “stringsFromApk” “C:\sdk\build-tools\android-4.4.2\androidTEST.apk” “C:\Windows\Temp\com.home.simple” e
n
info: [debug] No strings.xml for language ‘en’, getting default strings.xml
info: [debug] java -jar “C:\Program Files\nodejs\node_modules\appium\node_modules\appium-adb\jars\appium_apk_tools.jar” “stringsFromApk” “C:\sdk\build-tools\android-4.4.2\androidTEST.apk” “C:\Windows\Temp\com.home.simple”
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 push “C:\Windows\Temp\com.home.simple\strings.json” /data/local/tmp
info: [debug] Checking whether aapt is present
info: [debug] Using aapt from C:\sdk\build-tools\android-4.4.2\aapt.exe
info: [debug] processFromManifest: “C:\sdk\build-tools\android-4.4.2\aapt.exe” dump xm
ltree “C:\sdk\build-tools\android-4.4.2\androidTEST.apk” AndroidManifest.xml
info: [debug] Set app process to: com.home.simple
info: [debug] Not uninstalling app since server not started with --full-reset
info: [debug] Checking app cert for C:\sdk\build-tools\android-4.4.2\androidTEST.apk: java -jar “C:\Program Files\nodejs\node_modules\appium\node_modules\appium-adb\jars\verify.jar” “C:\sdk\build-tools\android-4.4.2\androidTEST.apk”
info: [debug] App already signed.
info: [debug] Zip-aligning C:\sdk\build-tools\android-4.4.2\androidTEST.apk
info: [debug] Checking whether zipalign is present
info: [debug] Using zipalign from C:\sdk\tools\zipalign.exe
info: [debug] zipAlignApk: “C:\sdk\tools\zipalign.exe” -f 4 “C:\sdk\build-tools\android-4.4.2\androidTEST.apk” “C:\Users\User\AppData\Local\Temp\appium114810-2596-1cqgzrm.tmp”
info: [debug] MD5 for app is 4e40e80878b34e04e1bead064d6a143e
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “ls /data/local/tmp/4e40e80878b34e04e1bead064d6a143e.apk”
info: [debug] Getting install status for com.home.simple
info: [debug] Getting device API level
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “getprop ro.build.version.sdk”
info: [debug] Device is at API Level 19
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “pm list packages -3 com.home.simple”
info: [debug] App is installed
info: App is already installed, resetting app
info: [debug] Running fast reset (stop and clear)
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “am force-stop com.home.simple”
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “pm cl
ear com.home.simple”
info: [debug] Forwarding system:4724 to device:4724
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 forward tcp:
4724 tcp:4724
info: [debug] Pushing appium bootstrap to device…
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 push “C:\Program Files\nodejs\node_modules\appium\build\android_bootstrap\AppiumBoots
trap.jar” /data/local/tmp/
info: [debug] Pushing settings apk to device…
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 install “C:\Program Files\nodejs\node_modules\appium\build\settings_apk\settings_apk-debug.apk”
info: [debug] Pushing unlock helper app to device…
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 install “C:\Program Files\nodejs\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
info: Starting App
info: [debug] Attempting to kill all ‘uiautomator’ processes
info: [debug] Getting all processes with ‘uiautomator’
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “ps ‘uiautomator’”
info: [debug] No matching processes found
info: [debug] Running bootstrap
info: [debug] spawning: C:\sdk\platform-tools\adb.exe -s emulator-5554 shell uiautomator runtestAppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [debug] [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
info: [debug] [BOOTSTRAP] [debug] Socket opened on port 4724
info: [debug] [BOOTSTRAP] [debug] Appium Socket Server Ready
info: [debug] [BOOTSTRAP] [debug] Loading json…
info: [debug] Waking up device if it’s not alive
info: [debug] Pushing command to appium work queue: [“wake”,{}]
info: [debug] [BOOTSTRAP] [debug] json loading complete.
info: [debug] [BOOTSTRAP] [debug] Registered crash watchers.
info: [debug] [BOOTSTRAP] [debug] Client connected
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“wake”,“params”:{}}
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] [BOOTSTRAP] [debug] Got command action: wake
info: [debug] [BOOTSTRAP] [debug] Returning result: {“value”:true,“status”:0}
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “dumpsys window”
info: [debug] Writing dumpsys output to C:\Program Files\nodejs\node_modules\app
ium.dumpsys.log
info: [debug] Screen already unlocked, continuing.
info: [debug] Pushing command to appium work queue: [“getDataDir”,{}]
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“getDataDir”,“params”:{}}
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] [BOOTSTRAP] [debug] Got command action: getDataDir
info: [debug] dataDir set to: /data
info: [debug] Getting device API level
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “getprop ro.build.version.sdk"info: [debug] [BOOTSTRAP] [debug] Returning result: {“value”:”/data",“status”:0}
info: [debug] Device is at API Level 19
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10
200000 -n com.home.simple/com.appemble.avm.dynamicapp.DynamicSplashActivity”
info: [debug] Waiting for pkg “com.home.simple” and activity “com.appemble.avm.dynamicapp.DynamicSplashActivity” to be focused
info: [debug] Getting focused package and activity
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “dumpsys window windows”
info: [debug] Setting auto webview
info: [debug] Getting a list of available webviews
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “cat /proc/net/unix”
info: [debug] Available contexts:
info: [debug] []
info: [debug] Available contexts: NATIVE_APP
info: [debug] Retrying context switch with timeout ‘60000’
info: [debug] Getting a list of available webviews
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “cat /proc/net/unix”
info: [debug] WEBVIEW_2006 mapped to pid 2006
info: [debug] Getting process name for webview
info: [debug] executing: “C:\sdk\platform-tools\adb.exe” -s emulator-5554 shell “ps”
info: [debug] Parsed pid: 2006 pkg: com.home.simple
info: [debug] from: u0_a52,2006,51,271408,42216,ffffffff,b6ed2614,R,com.home.simple
info: [debug] returning process name: com.home.simple
info: [debug] Available contexts: NATIVE_APP
info: [debug] [“WEBVIEW_com.home.simple”]
info: [debug] Available contexts: NATIVE_APP,WEBVIEW_com.home.simple
info: [debug] Connecting to chrome-backed webview
info: [debug] Creating Chrome session
info: [debug] Set chromedriver binary as: C:\Program Files\nodejs\node_modules\appium\build\chromedriver\windows\chromedriver.exe
info: [debug] Ensuring Chromedriver exists
info: [debug] Killing any old chromedrivers, running: FOR /F “usebackq tokens=5” %a in (netstat -nao ^| findstr /R /C:"9515 ") do (FOR /F “usebackq” %b in (TASKLIST /FI "PID eq %a" ^| findstr /I chromedriver.exe) do (IF NOT %b=="" TASKKILL /F /PID %b))
info: [debug] No old chromedrivers seemed to exist
info: [debug] Spawning chromedriver with: C:\Program Files\nodejs\node_modules\appium\build\chromedriver\windows\chromedriver.exe
info: [debug] [CHROMEDRIVER] Starting ChromeDriver (v2.10.267521) on port 9515
Only local connections are allowed.
info: [debug] Making http request with opts: {“url”:“http://127.0.0.1:9515/wd/hub/session",“method”:“POST”,“json”:{“sessionId”:null,“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.home.simple”,“androidUseRunningApp”:true,“androidDeviceSerial”:"emulator-5554”}}}}
error: Chromedriver create session did not work. Status was 200 and body was {“sessionId”:“de4b66bd16aa2175c2af5f96389fb088”,“status”:13,“value”:{“message”:“unknown error: unable to discover open pages\n (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86_64)”}}
info: [debug] Stopping logcat capture
info: [debug] Logcat terminated with code null, signal SIGTERM
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“shutdown”}
info: [debug] [BOOTSTRAP] [debug] Got command of type SHUTDOWN
info: [debug] Sent shutdown command, waiting for UiAutomator to stop…
info: [debug] [BOOTSTRAP] [debug] Returning result: {“value”:“OK, shutting down”,“status”:0}
info: [debug] [BOOTSTRAP] [debug] Closed client connection
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [debug] [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
info: [debug] [UIAUTOMATOR STDOUT] Time: 143.984
info: [debug] [UIAUTOMATOR STDOUT] OK (1 test)
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
info: [debug] UiAutomator shut down normally
info: [debug] Cleaning up android objects
info: [debug] Cleaning up appium session
error: Failed to start an Appium session, err was: Error: Did not get session redirect from Chromedriver
info: [debug] Error: Did not get session redirect from Chromedriver
at null. (C:\Program Files\nodejs\node_modules\appium\lib\devices\android\chromedriver.js:220:12)
at Request._callback (C:\Program Files\nodejs\node_modules\appium\lib\devices\common.js:116:5)
at Request.self.callback (C:\Program Files\nodejs\node_modules\appium\node_modules\request\request.js:121:22)
at Request.emit (events.js:98:17)
at Request. (C:\Program Files\nodejs\node_modules\appium\node_modules\request\request.js:985:14)
at Request.emit (events.js:117:20)
at IncomingMessage. (C:\Program Files\nodejs\node_modules\appium\node_modules\request\request.js:936:12)
at IncomingMessage.emit (events.js:117:20)
at _stream_readable.js:943:16
at process._tickDomainCallback (node.js:463:13)
info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: Did not get session redirect from Chromedriver)”,“origValue”:“Did not get session redirect from Chromedriver”},“sessionId”:null}
info: <-- POST /wd/hub/session 500 180418.447 ms - 214