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

Issue 645646 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

Invalidations not working on Android.

Project Member Reported by jnaveen@chromium.org, Sep 9 2016

Issue description

ENVIRONMENT and STATS
Chrome version: 54.0.2840.16

REPRO STEPS
1. Sign in to Chrome on a desktop.
2. Sign in to Chrome on Android.
3. Make some changes on desktop like adding bookmarks, autofill entries, open tabs etc
4. On Android chrome open chrome://invalidations

ACTUAL RESULTS
No invalidations are seen in the log and the changes made on desktop are not synced to Android.

EXPECTED RESULTS
Invalidations working properly and the changes made on desktop Chrome are synced to Android Chrome.

ADDITIONAL INFO
The root cause might be the same as mentioned in crbug.com/641888 but filing the bug as this is blocking Android sync tests.

 

Comment 1 by sky@chromium.org, Sep 9 2016

Cc: -sky@chromium.org
I'm not a good owner for sync related issues.

Comment 2 by zea@chromium.org, Sep 9 2016

Owner: s...@chromium.org
Status: Assigned (was: Untriaged)
The fix from 641888 has been merged to branch 2840, but there hasn't been a new build yet. The next beta build should have it. 

We can close this out once we verify the new build works properly.

Comment 3 by s...@chromium.org, Sep 14 2016

Status: Fixed (was: Assigned)
Current Android Dev build is 54.0.2840.25, and it contains agreive@'s fix https://chromium.googlesource.com/chromium/src/+log/54.0.2840.16..54.0.2840.25?pretty=fuller&n=10000 . On a test device I am receiving invalidations, resolving.
Status: Verified (was: Fixed)
Verified in 54.0.2840.25, invalidations are working fine.

Sign in to add a comment