New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 666760 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 2
Type: Bug

Blocked on:
issue 663475



Sign in to add a comment

QR Scanner is not working on every alternative launch

Project Member Reported by srikanthg@chromium.org, Nov 18 2016

Issue description

App Version: 56.0.2923.0 canary
iOS Version: 10.1, 9.3.5
Device: iPhone6 plus, iPhone7, iPhone SE
URL: na

Steps to reproduce:
  1. Launch Google Chrome and background the app
  2. Launch QR Scanner (via spotlight or Force touch)
  3. Scan any qr code and background the app
  4. Launch Scanner again

Observed results: Observe that scanner UI is displayed but camera is not seen. Black screen is displayed.

Expected results: Scanner should work.

Note: Dismissing the Scanner and launching again works fine. Sometimes its not working on every alternative launch and sometimes it seems like not working when the app is backgrounded quickly before loading the webpage and then scanner is launched. 

Number of times you were able to reproduce: 3/5
Bug reproducible after clean install: Yes
Bug reproducible after clearing cache and cookies: Yes
Bug reproducible on Chrome Mobile on Android: NA
Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA
Bug reproducible on current stable build (App Version, iOS Version): M54 NA
Bug reproducible on the current beta channel build (App Version, iOS Version): M55 NA

Link to video/image: https://drive.google.com/file/d/0B-xmXLQhjeKuZ3Q5anNEcTQ0LTQ/view
 

Comment 1 by pkl@chromium.org, Nov 21 2016

Labels: ReleaseBlock-Stable
Status: Assigned (was: Untriaged)

Comment 2 Deleted

Labels: -Restrict-View-Google
Just had this happen on a fresh install of today's Canary (57.0.2947.0).
On the first launch of the QR scanner, I had the same black screen.  Subsequent launches were fine.  I think the app was backgrounded first but not recently.
Blockedon: 663475

Comment 5 by jif@chromium.org, Dec 13 2016

Issue 656598 has been merged into this issue.
Project Member

Comment 6 by bugdroid1@chromium.org, Dec 16 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/bd091891ccaf5776fcbc80c7366c529ec4d4a34f

commit bd091891ccaf5776fcbc80c7366c529ec4d4a34f
Author: jif <jif@google.com>
Date: Fri Dec 16 13:24:28 2016

Comment 7 by jif@chromium.org, Dec 16 2016

Status: Fixed (was: Started)
Bug should be fixed in ToT.
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-56; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-56 label, otherwise remove Merge-TBD label. Thanks.
Project Member

Comment 9 by sheriffbot@chromium.org, Dec 16 2016

Labels: Merge-Review-56 Hotlist-Merge-Review
This bug requires manual review: No test file found in commits.
Please contact the milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), gkihumba@(cros), bustamante@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 10 by sheriffbot@chromium.org, Dec 16 2016

This bug requires manual review: No test file found in commits.
Please contact the milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), gkihumba@(cros), bustamante@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
 srikanthg@ please verify in next canary.

Comment 12 by dimu@google.com, Dec 16 2016

Labels: -Merge-Review-56 -Hotlist-Merge-Review
[Automated comment] removing mislabelled Merge-Review-56, Hotlist-Merge-Review

Comment 13 by jif@chromium.org, Dec 20 2016

Cc: srikanthg@chromium.org
srikanthg> bug should be fix in the latest canary.

Comment 14 by jif@chromium.org, Dec 20 2016

Labels: Merge-Request-56

Comment 15 by dimu@chromium.org, Dec 20 2016

Labels: -Merge-Request-56 Merge-Approved-56 Hotlist-Merge-Approved
Your change meets the bar and is auto-approved for M56 (branch: 2924)
Project Member

Comment 16 by bugdroid1@chromium.org, Dec 20 2016

Labels: -merge-approved-56 Merge-Merged-2924
The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/d19846b4d6e392546e9ebb96e787e72ee9d86704

commit d19846b4d6e392546e9ebb96e787e72ee9d86704
Author: jif <jif@google.com>
Date: Fri Dec 16 13:24:28 2016

Status: Verified (was: Fixed)
Verified. QR Scanner is working fine on every launch.
Device: iPhone plus, iPhone SE
iOS: 10.2.1, 9.3.5
Build: 56.0.2924.48 beta.
Verified the issue on the latest canary on iPhone 56.0.292475 beta
tested on iPhone7(iOS10).
QR scanner works fine on every launch 
Project Member

Comment 19 by sheriffbot@chromium.org, Mar 8 2017

Labels: -Merge-TBD

Sign in to add a comment