How to install Chrome Browser in Android Emulator

Support
1

I see many people tried launching Chrome in Android Emulators.

Surfed around internet to find a solution, but many said Chromium has to be installed etc…

Whoever using Chrome browser in this forum also installed Chromium etc…???

Is there any easy way to install Chrome in emulator?

Does anybody have success launching application in default browser that comes with Emulator?

Please help.

Thanks in advance,
Uday

1 Like
2

I’ve used the below capabilities to launch the default Android browser.

DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability(MobileCapabilityType.DEVICE_NAME,“ANDROID”);
capabilities.setCapability(MobileCapabilityType.PLATFORM, “ANDROID”);
capabilities.setCapability(MobileCapabilityType.BROWSER_NAME, “BROWSER”);

3

For stock browser:
browserName capability as “browser”

For Chrome:
Acquire the Chrome apk build for your required version and architecture (ARM, x86).
Install Chrome apk on emulator by booting the device and executing “adb install *filepath”

After that, specifying the browserName capability should open Chrome. You could also do it programmatically by specifying the Chrome apk like would be done for any other app.

4

@James_Kim,

Did you get a chance to run couple of operations once the browser is opened. Why i am asking is, Appium just launches the browser(in fact it is not launching Facebook page as i intended) and in fraction of a second, it closes the browser and coming to Home screen.

As per Appium log also i am thinking they are expecting Chrome browser to be run on emulator. Please find Appium log or let me know if i am missing something or my configurations are wrong.

> info: --> POST /wd/hub/session {"desiredCapabilities":{"browserName":"BROWSER","platformName":"Android","deviceName":"Testing","platform":"ANDROID"}}
> info: Client User-Agent string: Apache-HttpClient/4.3.4 (java 1.5)
> 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
> info: Set mode: Proxying straight through to Chromedriver
> info: [debug] Looks like we want chrome on android
> info: [debug] Creating new appium session 16e85747-74fc-45d4-80ad-e2e7d77c480c
> info: [debug] Using fast reset? true
> info: [debug] Preparing device for session
> info: [debug] Not checking whether app is present since we are assuming it's already on the device
> info: [debug] Checking whether adb is present
> info: [debug] Using adb from D:\UD\sdk\tools\adb.exe
> info: Retrieving device
> info: [debug] Trying to find a connected android device
> info: [debug] Getting connected devices...
> info: [debug] executing cmd: D:\UD\sdk\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 cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 wait-for-device
> info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell "echo 'ready'"
> info: [debug] Starting logcat capture
> info: [debug] Pushing unlock helper app to device...
> info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 install "D:\softies\Programs\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk"
> info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell "dumpsys window"
> info: [debug] Screen already unlocked, continuing.
> info: [debug] Forwarding system:4724 to device:4724
> info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 forward tcp:4724 tcp:4724
> info: [debug] Pushing appium bootstrap to device...
> info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 push "D:\\softies\\Programs\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/
> info: Starting App
> info: [debug] Attempting to kill all 'uiautomator' processes
> info: [debug] Getting all processes with 'uiautomator'
> info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell "ps 'uiautomator'"
> info: [debug] Attempting to kill process 2065
> info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell "kill 2065"
> info: [debug] Running bootstrap
> info: [debug] spawning: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
> info: [debug] UiAutomator exited
> info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell "echo 'ping'"
> info: [debug] Attempting to uninstall app
> error: UiAutomator quit before it successfully launched
> info: [debug] Not uninstalling app since server not started with --full-reset
> info: [debug] Cleaning up android objects
> 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] [BOOTSTRAP] [debug] json loading complete.
> info: [debug] [BOOTSTRAP] [debug] Registered crash watchers.
> info: [debug] Pushing command to appium work queue: ["getDataDir",{}]
> info: [debug] [BOOTSTRAP] [debug] Client connected
> info: [debug] dataDir set to: /data
> info: [debug] Creating Chrome session
> info: [debug] Set chromedriver binary as: D:\softies\Programs\Appium\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] [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] [BOOTSTRAP] [debug] Returning result: {"status":0,"value":"\/data"}
> info: [debug] No old chromedrivers seemed to exist
> info: [debug] Spawning chromedriver with: D:\softies\Programs\Appium\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.android.browser","androidActivity":"com.android.browser.BrowserActivity","androidDeviceSerial":"emulator-5554"}}}}
> info: [debug] [CHROMEDRIVER STDERR] [0.008][SEVERE]: Could not bind socket to 127.0.0.1:9515
> info: [debug] [CHROMEDRIVER] Port not available. Exiting...
> info: [debug] Chromedriver exited with code 1
> info: [debug] Getting connected devices...
> info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 devices
> info: [debug] 1 device(s) connected
> info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell "am force-stop com.android.browser"
> info: [debug] Stopping logcat capture
> info: [debug] Logcat terminated with code null, signal SIGTERM
> info: [debug] Cleaning up appium session
> error: Chromedriver create session did not work. Status was 200 and body was {"sessionId":"7fde11aa9f9d0473627c765af031ad39","status":13,"value":{"message":"unknown error: Chrome version must be >= 33.0.1750.0\n  (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86)"}}
> 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.<anonymous> (D:\softies\Programs\Appium\node_modules\appium\lib\devices\android\chromedriver.js:222:12)
>     at Request._callback (D:\softies\Programs\Appium\node_modules\appium\lib\devices\common.js:121:5)
>     at Request.self.callback (D:\softies\Programs\Appium\node_modules\appium\node_modules\request\request.js:121:22)
>     at Request.EventEmitter.emit (events.js:98:17)
>     at Request.<anonymous> (D:\softies\Programs\Appium\node_modules\appium\node_modules\request\request.js:985:14)
>     at Request.EventEmitter.emit (events.js:117:20)
>     at IncomingMessage.<anonymous> (D:\softies\Programs\Appium\node_modules\appium\node_modules\request\request.js:936:12)
>     at IncomingMessage.EventEmitter.emit (events.js:117:20)
>     at _stream_readable.js:920:16
>     at process._tickDomainCallback (node.js:459: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 14972.154 ms - 214

Following is the code which i am trying to run:

import io.appium.java_client.android.AndroidDriver;
import io.appium.java_client.remote.MobileCapabilityType;

import java.io.File;
import java.net.URL;

import org.openqa.selenium.remote.DesiredCapabilities;
import org.testng.annotations.*;


public class LaunchMobileBrowser 
{
     private AndroidDriver driver;
     @BeforeTest
     public void setup() throws Exception 
     {
         DesiredCapabilities capabilities = new DesiredCapabilities();
         capabilities.setCapability(MobileCapabilityType.DEVICE_NAME,"Testing");
         capabilities.setCapability(MobileCapabilityType.PLATFORM, "ANDROID");
         capabilities.setCapability(MobileCapabilityType.BROWSER_NAME, "BROWSER");
         driver = new AndroidDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);
     }
     
     @Test
     public void launchBrowser()
     {
         driver.get("http://www.facebook.com");
     }
}
5

@Simon,

I downloaded the Chrome.apk file from internet and when i install it, it is throwing an error message saying “INSTALL_FAILED_NO_MATCHING_ABIS”.

I surfed around internet, and my understanding from this error is, it is not right apk file.

So can you please point out to right apk file path? If you have success over with your chrome.apk file, can you place it in github or somewhere and share the path?

6

Can you try with updated version of ChromeDriver server? There was an issue with a previous version of Appium and the ChromeDriver.exe that came pre-bundled with.

You can get latest one from: Sign in - Google Accounts

Replace the newly downloaded ChromeDriver.exe file with the one located in “D:\softies\Programs\Appium\node_modules\appium\build\chromedriver\windows\chromedriver.exe”

Below is a very basic script (it just opens up a single page) that I have that works. This is using appium v1.3.6, chromedriver v2.14, JUnit4, android 5.0 avd, and default browser. Hopefully this helps get you started.

import java.net.URL;
import java.util.concurrent.TimeUnit;
import org.junit.After;
import org.junit.Before;
import org.junit.Test;
import org.openqa.selenium.remote.DesiredCapabilities;
import io.appium.java_client.android.AndroidDriver;
import io.appium.java_client.remote.MobileCapabilityType;

public class AppiumWebTest {
private AndroidDriver driver;

@Before
public void setUp() throws Exception
{
    DesiredCapabilities capabilities = new DesiredCapabilities();
    capabilities.setCapability(MobileCapabilityType.DEVICE_NAME,"ANDROID");
    capabilities.setCapability(MobileCapabilityType.PLATFORM, "ANDROID");
    capabilities.setCapability(MobileCapabilityType.BROWSER_NAME, "BROWSER");

    driver = new AndroidDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);
    driver.manage().timeouts().implicitlyWait(30, TimeUnit.SECONDS);
}

@Test
public void test() throws Exception
{
  driver.get("http://appium.io/");
}

@After
public void tearDown() throws Exception
{
	driver.quit();
}

}

1 Like
7

One more basic question, please done hesitate.

If we have to work with default browser comes with emulator, what is the need of having or installing this chromedriver.exe?

8

I tried with updated ChromeDriver, still sees the same problem:

I am using Appium 1.3.4

Following are Appium Logs:

info: → POST /wd/hub/session {“desiredCapabilities”:{“browserName”:“BROWSER”,“platformName”:“Android”,“deviceName”:“Testing”,“platform”:“ANDROID”}}
info: Client User-Agent string: Apache-HttpClient/4.3.4 (java 1.5)
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
> info: Set mode: Proxying straight through to Chromedriver
> info: [debug] Looks like we want chrome on android
info: [debug] Creating new appium session 68eb5a25-04e9-4e61-afc8-03144ab40dcc
info: [debug] Using fast reset? true
info: [debug] Preparing device for session
info: [debug] Not checking whether app is present since we are assuming it’s already on the device
info: [debug] Checking whether adb is present
info: [debug] Using adb from D:\UD\sdk\tools\adb.exe
info: Retrieving device
info: [debug] Trying to find a connected android device
info: [debug] Getting connected devices…
info: [debug] executing cmd: D:\UD\sdk\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 cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 wait-for-device
info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell “echo ‘ready’”
info: [debug] Starting logcat capture
info: [debug] Pushing unlock helper app to device…
info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 install “D:\softies\Programs\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell “dumpsys window”
info: [debug] Screen already unlocked, continuing.
info: [debug] Forwarding system:4724 to device:4724
info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 forward tcp:4724 tcp:4724
info: [debug] Pushing appium bootstrap to device…
info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 push “D:\softies\Programs\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/
info: Starting App
info: [debug] Attempting to kill all ‘uiautomator’ processes
info: [debug] Getting all processes with ‘uiautomator’
info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell “ps ‘uiautomator’”
info: [debug] Attempting to kill process 2100
info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell “kill 2100”
info: [debug] Running bootstrap
info: [debug] spawning: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
info: [debug] UiAutomator exited
info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell “echo ‘ping’”
info: [debug] Attempting to uninstall app
error: UiAutomator quit before it successfully launched
info: [debug] Not uninstalling app since server not started with --full-reset
info: [debug] Cleaning up android objects
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] [BOOTSTRAP] [debug] json loading complete.
info: [debug] Pushing command to appium work queue: [“getDataDir”,{}]
info: [debug] [BOOTSTRAP] [debug] Registered crash watchers.
info: [debug] dataDir set to: /data
info: [debug] Creating Chrome session
info: [debug] Set chromedriver binary as: D:\softies\Programs\Appium\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] [BOOTSTRAP] [debug] Client connected
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] [BOOTSTRAP] [debug] Returning result: {“status”:0,“value”:“/data”}
info: [debug] No old chromedrivers seemed to exist
info: [debug] Spawning chromedriver with: D:\softies\Programs\Appium\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.android.browser”,“androidActivity”:“com.android.browser.BrowserActivity”,“androidDeviceSerial”:"emulator-5554”}}}}
info: [debug] [CHROMEDRIVER STDERR] [0.007][SEVERE]: Could not bind socket to 127.0.0.1:9515
> info: [debug] [CHROMEDRIVER] Port not available. Exiting…
info: [debug] Chromedriver exited with code 1
info: [debug] Getting connected devices…
info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 devices
info: [debug] 1 device(s) connected
info: [debug] executing cmd: D:\UD\sdk\tools\adb.exe -s emulator-5554 shell “am force-stop com.android.browser”
info: [debug] Stopping logcat capture
info: [debug] Logcat terminated with code null, signal SIGTERM
info: [debug] Cleaning up appium session
> error: Chromedriver create session did not work. Status was 200 and body was {“sessionId”:“14d43e8615efc013c6581fa2c3858bd3”,“status”:21,“value”:{“message”:“timeout: Adb command timed out after 30 seconds\n (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86)”}}
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. (D:\softies\Programs\Appium\node_modules\appium\lib\devices\android\chromedriver.js:222:12)
at Request._callback (D:\softies\Programs\Appium\node_modules\appium\lib\devices\common.js:121:5)
at Request.self.callback (D:\softies\Programs\Appium\node_modules\appium\node_modules\request\request.js:121:22)
at Request.EventEmitter.emit (events.js:98:17)
at Request. (D:\softies\Programs\Appium\node_modules\appium\node_modules\request\request.js:985:14)
at Request.EventEmitter.emit (events.js:117:20)
at IncomingMessage. (D:\softies\Programs\Appium\node_modules\appium\node_modules\request\request.js:936:12)
at IncomingMessage.EventEmitter.emit (events.js:117:20)
at _stream_readable.js:920:16
at process._tickDomainCallback (node.js:459: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 39847.660 ms - 214
info: [debug] Logcat terminated with code 0, signal null

9

Could you double check that the chromedriver has been updated? I see in your logs that it is still referencing v2.10. I just tested it out by downloading v2.10 and I get the same error. Updating chromedriver to v2.14, the error does not occur.

If you open up command prompt and type the below line, you can find out the current version you have. “D:\softies\Programs\Appium\node_modules\appium\build\chromedriver\windows\chromedriver.exe -v”

This is your log indicating chromedriver version.

info: [debug] Spawning chromedriver with: D:\softies\Programs\Appium\node_modules\appium\build\chromedriver\windows\chromedriver.exe
info: [debug] [CHROMEDRIVER] Starting ChromeDriver (v2.10.267521) on port 9515

10

It sounds like you need a x86 build of the apk. I’m unsure of the legality of distributing the file, so you will have to obtain that yourself. You can do that by running a genymotion emulator, installing the play store, downloading chrome, then extracting the apk.

11

@James_Kim,

Thank you so much for looking into the logs and figuring it out my problem.

Earlier, though i copied the chromedriver, somehow it was now copied properly.

Now i copied it properly and checked the version and ran the same code. It is working good and as expected.

Ton thanks for figuring out the problem and helping me.

Thanks,
Uday

12

Hello,
@UD. could you tell me, did you successfully run your appium tests on Android Browser (not Chrome/Chromium Browser)? I downloaded the latest chromedriver exe (2.19) and put it to C:\Program Files (x86)\Appium\node_modules\appium\build\chromedriver\windows. Logs are the same as in 2.14, Appium is probably trying to find Chrome

Got response with status 200: {“sessionId”:“79e91b839b3f2b381ed54f39e613c969”,“status”:100,“value”:{“message”:"chrome not reachable\n (Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Wind…

You can see my full logs in other topic: Difficulty with Browser/Chromium on android emulator and chromedriver - #10 by czarnykwarc

Workaround is to create emulator in higher settings (API 23, Android 6) but what if I also need tests on older version of Android?

1 Like
13

Hello,

I tried with command $ ./adb install ChromeBrowser-Google.apk but returns error like -

ChromeBrowser-Google.apk: 1 file pushed. 48.6 MB/s (47966234 bytes in 0.941s)
pkg: /data/local/tmp/ChromeBrowser-Google.apk
Failure [INSTALL_FAILED_NO_MATCHING_ABIS]

Can you please help me on this!

Thanks in advance.

14

Face the same problem with my chrome app.