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

Issue 894173 link

Starred by 2 users
Status: Assigned
Owner:
melandory@chromium.org
Cc:
mastiz@chromium.org
█ tschumann@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Recent Tabs for other devices not keeping up-to-date on Android

Reported by dvanh...@gmail.com, Oct 10 
Steps to reproduce the problem:
1. Pin browser so it won't be closed by the OS.
2. Load 80 tabs. (not sure if this is an important part of the process, but I've included it anyway. If you need suggestions, loading up stories from www.notalwaysright.com can be entertaining)
3. Start a new tab, then open the Recent Tabs screen.

What is the expected behavior?
Tabs from other devices on the same account should be synced to within five minutes, or less if they're still open.

What went wrong?
Tabs are at least 12 hours old. Even leaving it open for twenty minutes doesn't update the list.

Did this work before? Yes 

Chrome version: 69.0.3497.100  Channel: stable
OS Version: 8.0.0 on LG G6
Flash Version: 

I've been having this problem for at least a whole week, and the only way to fix this is to kill the browser and start it up again.

Not even the suggestion of forcing an account sync in the OS's account management app does anything to fix this.

Restart appears to be the only time tab data is synced from other devices.

I'm having to kill and restart the browser every day I want to load tabs from my laptop onto my phone.

Comment 1 by chelamcherla@chromium.org, Oct 12

Labels: Needs-triage-Mobile

Comment 2 by melandory@chromium.org, Oct 15

Labels: Sync-Triaged
Owner: melandory@chromium.org

Comment 3 by melandory@chromium.org, Oct 15 

Hey, thanks for reporting and I'm sorry that you're experiencing this issue.

I need a bit more information. Could you please open chrome://invalidations page on you phone, take a screenshot and attach it to the bug.

Thanks!

Comment 4 by dvanh...@gmail.com, Oct 25 

I apologize for the delay, but it appears the bug has been fixed. I'm currently running 70.0.3538.64 now, and it's been working very reliably. Thanks!

Comment 5 by dpcn...@gmail.com, Dec 2 

Hasn't been fixed. Attached is my invalidations page.

Restarting the app seems to be the only way to force a sync.

Chrome 70.0.3538.80 stable channel.
invalidations.png
107 KB View Download

Comment 6 by mastiz@chromium.org, Dec 2 

I'm assuming the history page was open at the time the screenshot was taken on Android.

Looks good to me. melandory@: anything fishy there?

Reporter/dvanhumb@: a few questions:
1. Do you have any third device (preferably desktop) to confirm the issue is on the receiving end (Android), and not the initiating device (desktop?)?

2. In doubt, for the desktop device, please paste chrome://signin-internals and chrome://sync-internals.

Comment 7 by benhenry@google.com, Jan 11

Status: Assigned (was: Unconfirmed)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment