ChromeDriver Android bot: Unable to install latest Chrome Stable on build91-b1 |
|||
Issue descriptionAfter the Android device attached to build91-b1 was re-flashed a couple of days ago, I wasn't able to install the latest Chrome Stable on it. I ran the following command from the home directory: ./adb install -r ChromeStable.apk And received the following error: Failure [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] How do I resolve this error?
,
Mar 14 2018
I wasn't able to uninstall the app, probably because Chrome is a built-in app. Right now the device is flashed with a very old Android, version 4.4.4. I wonder if it would help if it is flashed to a newer version, such as 6.0.
,
Mar 14 2018
On my devices it is 6.0.1, so it would be nice to have exactly the same version. adb shell getprop ro.build.version.release 6.0.1
,
Mar 14 2018
I can do this.
,
Mar 14 2018
$ ./adb -d shell getprop ro.build.fingerprint google/hammerhead/hammerhead:6.0.1/MOB31V/3693677:userdebug/dev-keys Effective starting with https://uberchromegw.corp.google.com/i/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29/builds/39452
,
Mar 14 2018
So is the device on Android build bot now running Android 6.0.1 ?
,
Mar 14 2018
Yes it is.
,
Mar 14 2018
Great! Thank you!
,
Mar 14 2018
I have successfully installed the latest Chrome Stable and Chrome Beta on the device. Thanks!
,
Mar 15 2018
btw, this apk installation problem sounded familiar. crbug.com/739373
,
Mar 15 2018
I'm encountering a new issue with this device. The WebView currently installed on the device is incompatible with ChromeDriver. However, attempt to update it failed: chrome-bot@build91-b1:(Linux 14.04):~$ ./adb install -r android-B0urB0N%2F65.0.3325.109%2Farm%2FAndroidWebview.apk android-B0urB0N%2F65.0.3325.109%2Farm%...d. 9.1 MB/s (32704207 bytes in 3.416s) pkg: /data/local/tmp/android-B0urB0N%2F65.0.3325.109%2Farm%2FAndroidWebview.apk Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE] The same error code was mentioned in crbug.com/739373 , but it isn't clear how this was fixed. Any idea how to resolve this error? |
|||
►
Sign in to add a comment |
|||
Comment 1 by bpastene@chromium.org
, Mar 14 2018