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

Issue 724711 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Nov 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 747601



Sign in to add a comment

EasyUnlock v2: Remove background page in app

Project Member Reported by tengs@chromium.org, May 20 2017

Issue description

Because we will migrate fully to a native implementation, the app should only be used for the set up flow. All existing CryptAuth and authentication logic should be removed.
 

Comment 1 by tengs@chromium.org, May 20 2017

Blocking: 724708

Comment 2 by tengs@chromium.org, May 25 2017

Labels: M-62

Comment 3 by tengs@chromium.org, Jun 21 2017

Blocking: -724708

Comment 4 by tengs@chromium.org, Jul 21 2017

Blocking: 747601

Comment 5 by tengs@chromium.org, Aug 3 2017

Cc: semenzato@chromium.org tbarzic@chromium.org tengs@chromium.org vapier@chromium.org
 Issue 679860  has been merged into this issue.
Tim, can you update this with a bit more detail of what it entails? What is the app doing right now that should be removed? Note that with the move to unified "better together" setup, we'll probably need to switch to a webUI instead of a chrome app, but understanding which pieces of the existing easyunlock app are actively being used by v2 is important to planning out our design.

Comment 7 by tengs@google.com, Dec 4 2017

The background page of the app contains the old EasyUnlock v1 functionality and is currently suppressed for EasyUnlock v2 (unless you disable the BLE flag). This bug is basically for removing the flag and completely removing the background page implementation of EasyUnlock v1.
Components: -UI>ProximityAuth
Components: UI>SmartLock
Status: WontFix (was: Assigned)

Sign in to add a comment