New issue
Advanced search Search tips

Issue 690152 link

Starred by 3 users
Status: Started
Owner:
pkotw...@chromium.org
Cc:
hanxi@chromium.org
pkotw...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Add logging to make it easy to determine why WebAPK install fails

Project Member Reported by pkotw...@chromium.org, Feb 8 2017 
When a WebAPK install fails it is currently impossible to tell from the logcat whether the failure was because of:
- A bug in Chrome
- A bug in the WebAPK server
- A bug in Google Play

We should add logging to make it easy to differentiate between these three cases

Comment 1 by hanxi@chromium.org, Feb 8 2017 

We can only tell it is a bug in WebApk server if server failed to mint a APK before Chrome send install request to Google Play. Once the request is sent, we can't tell exactly whether the bug is in server or Google Play. We might expect a flag in the server's response if minting a WebAPK failed on the server.

Comment 2 by pkotw...@chromium.org, Feb 9 2017

Owner: pkotw...@chromium.org
Status: Started (was: Untriaged)
Project Member

Comment 3 by bugdroid1@chromium.org, Feb 13 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6d3fe481d1e1510b36c74ae18611da5646d0cff6

commit 6d3fe481d1e1510b36c74ae18611da5646d0cff6
Author: pkotwicz <pkotwicz@chromium.org>
Date: Mon Feb 13 20:45:02 2017

Add logs for WebAPK server failures

This will make it easier to determine whether a WebAPK cannot be installed due
to a WebAPK server error.

BUG=690152

Review-Url: https://codereview.chromium.org/2687163002
Cr-Commit-Position: refs/heads/master@{#450072}

[modify] https://crrev.com/6d3fe481d1e1510b36c74ae18611da5646d0cff6/chrome/browser/android/webapk/webapk_installer.cc
►

Sign in to add a comment