I have installed the chrome driver - version 37.0 and source -com.android.chrome-1.apk
Started the dab command and device is connecting properly.
Getting below error -
info: Welcome to Appium v1.2.1 (REV 2a4b624a708e580709006b697dc4c9c4e3007863)
debug: Non-default server args: {“app”:“browser”,“sessionOverride”:true,“deviceName”:“UHG”,“platformName”:“Android”,“platformVersion”:“4.4”,“automationName”:“Appium”,“browserName”:“Chrome”,“defaultCommandTimeout”:7200}
info: Appium REST http interface listener started on 0.0.0.0:4723
info: LogLevel: debug
info: --> GET /wd/hub/status {}
debug: Responding to client with success: {“status”:0,“value”:{“build”:{“version”:“1.2.1”,“revision”:“2a4b624a708e580709006b697dc4c9c4e3007863”}}}
info: <-- GET /wd/hub/status 200 8.473 ms - 104 {“status”:0,“value”:{“build”:{“version”:“1.2.1”,“revision”:“2a4b624a708e580709006b697dc4c9c4e3007863”}}}
info: --> GET /wd/hub/status {}
debug: Responding to client with success: {“status”:0,“value”:{“build”:{“version”:“1.2.1”,“revision”:“2a4b624a708e580709006b697dc4c9c4e3007863”}}}
info: <-- GET /wd/hub/status 200 2.205 ms - 104 {“status”:0,“value”:{“build”:{“version”:“1.2.1”,“revision”:“2a4b624a708e580709006b697dc4c9c4e3007863”}}}
info: --> POST /wd/hub/session {“desiredCapabilities”:{“platformVersion”:“4.3”,“platformName”:“Android”,“deviceName”:“UHG”,“browserNamex”:“Chrome”,“appium-version”:“1.0”}}
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. : browserNamex, appium-version
debug: Looks like we want chrome on android
debug: Creating new appium session a2980ff3-0221-4055-ba5c-7c094c54180e
debug: Preparing device for session
debug: Not checking whether app is present since we are assuming it’s already on the device
debug: Checking whether adb is present
debug: Using adb from /Users/jitendrakumar/Desktop/android/sdk/platform-tools/adb
info: Retrieving device
debug: Trying to find a connected android device
debug: Getting connected devices…
debug: executing: “/Users/jitendrakumar/Desktop/android/sdk/platform-tools/adb” devices
debug: 1 device(s) connected
info: Found device 43001beab8cb1161
debug: Setting device id to 43001beab8cb1161
debug: Waiting for device to be ready and to respond to shell commands (timeout = 5)
debug: executing: “/Users/jitendrakumar/Desktop/android/sdk/platform-tools/adb” -s 43001beab8cb1161 wait-for-device
debug: executing: “/Users/jitendrakumar/Desktop/android/sdk/platform-tools/adb” -s 43001beab8cb1161 shell “echo ‘ready’”
debug: Starting logcat capture
debug: Pushing unlock helper app to device…
debug: executing: “/Users/jitendrakumar/Desktop/android/sdk/platform-tools/adb” -s 43001beab8cb1161 install “/Applications/Appium.app/Contents/Resources/node_modules/appium/build/unlock_apk/unlock_apk-debug.apk”
debug: executing: “/Users/jitendrakumar/Desktop/android/sdk/platform-tools/adb” -s 43001beab8cb1161 shell “dumpsys window”
debug: Writing dumpsys output to /Applications/Appium.app/Contents/Resources/node_modules/appium/.dumpsys.log
debug: Screen already unlocked, continuing.
debug: Creating Chrome session
debug: Ensuring Chromedriver exists
debug: Killing any old chromedrivers, running: ps -ef | grep /Applications/Appium.app/Contents/Resources/node_modules/appium/build/chromedriver/mac/chromedriver | grep -v grep |grep -e ‘–port=9515$’ | awk ‘{ print $2 }’ | xargs kill -15
debug: Successfully cleaned up old chromedrivers
debug: Spawning chromedriver with: /Applications/Appium.app/Contents/Resources/node_modules/appium/build/chromedriver/mac/chromedriver
debug: [CHROMEDRIVER] Starting ChromeDriver (v2.10.267517) on port 9515
Only local connections are allowed.
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.android.browser”,“androidActivity”:“com.android.browser.BrowserActivity”,“androidDeviceSerial”:"43001beab8cb1161”}}}}
error: Chromedriver create session did not work. Status was 200 and body was {“sessionId”:“e70c1dff331b9b35ce5e4b974ae3d47e”,“status”:13,“value”:{“message”:“unknown error: com.android.browser is not installed on device 43001beab8cb1161\n (Driver info: chromedriver=2.10.267517,platform=Mac OS X 10.9.2 x86_64)”}}
debug: Cleaning up appium session
error: Failed to start an Appium session, err was: Error: Did not get session redirect from Chromedriver
info: <-- POST /wd/hub/session 500 3491.489 ms - 214
debug: Error: Did not get session redirect from Chromedriver
at null. (/Applications/Appium.app/Contents/Resources/node_modules/appium/lib/devices/android/chromedriver.js:203:12)
at Request._callback (/Applications/Appium.app/Contents/Resources/node_modules/appium/lib/devices/common.js:116:5)
at Request.self.callback (/Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/request/request.js:121:22)
at Request.emit (events.js:98:17)
at Request. (/Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/request/request.js:985:14)
at Request.emit (events.js:117:20)
at IncomingMessage. (/Applications/Appium.app/Contents/Resources/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)
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: --> GET /wd/hub/status {}