-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Android] Sync v2 takes too long to auto-update after waking phone up from sleep #11714
Comments
today I noticed the same on my daily desktop browser, all types have Backed off status,
|
Marking P2 because I have now the profile with exactly the same problem. |
Today I encountered this bug on my Surface Pro Windows tablet, except that it never seems to come out of I have a feeling Sync v2 doesn't handle devices coming back from sleep very well. To fix the issue below, I had to leave the sync chain on my tablet and rejoin. The |
It is unclear why exactly that happened and impossible to find out for the current moment. The way to recover I still continue look on my sync chain, maybe will have more luck with guaranteed reproducing of the issue. |
@AlexeyBarabash This issue is pretty reproducible on Android. It happens almost 100% of the time after waking the phone up from sleep and launching Brave. It takes a good 2-3 minutes before status changes to green. Perhaps the issue we're seeing on desktop, your SERVER_RETURN_TRANSIENT_ERROR and my SERVER_RETURN_CONFLICT may have different root causes than on Android? |
if you see the yellow status for 3 minutes after and then it goes to green - this may be considered as expected. When there are conflicts this means device cannot send own changes into the sync server, the device must download the latest changes, resolve conflict locally (accept remote/merge/overwrite with local) and then send the changes back to server.
Yes, mine was observed on the desktop and hadn't gone away no matter how long I waited, it had been there until I re-toggled the sync category, |
This would mean that we're waiting up to 3 minutes for things like Open Tab sync and Send Tab to Device. That isn't a good user experience. Things seem to be syncing much faster in regular Chrome.
Shouldn't the browser resolve those changes automatically? Seems a bit intense to expect the user to go to |
I reproduced this again today. I don't know the exact steps otherwise I would list them here, but I was testing out different shield configuration settings under Settings->Shields, clearing out Site and Shield settings, and restarting the browser frequently. After a few rounds of changing those settings and restarting the browser, I discovered that I was again not able to effectively send tabs from one device to another. Perhaps try reproducing by toggling Shields global settings a few times and restarting the browser in rapid succession? EDIT: I should also mention that my computer experienced a few hard crashes as well, so maybe Brave was in the middle of sync when that happened? Not sure, really wish I could provide more details and steps to reproduce, but it is what it is. |
I am now getting SERVER_RETURN_TRANSIENT_ERROR on at least one of my devices every other day. It makes Sync horribly unreliable. Has there been any progress on this? |
I find Sync v2 unreliable on the desktop under Version 1.20.85 Chromium: 88.0.4324.96 (Official Build) beta (64-bit) between two Win10 20H2 computers. Computer A sees all the Open Tabs from computer B yet computer B only sees two open tabs from computer A. starting a new sync chain fixes it but it will probably go again. Computer A is a laptop and as such is hibernating each day and I am wondering if that is the issue with computer A not being able to see the Open Tabs reliably even when the laptop has been in use for hours. |
it was working fine on windows machine (3 windows 10 desktops). |
Has there been any updates on this? This bug really hinders the sync experience on Android and is a frequent source of complaints on the Brave subreddit. Currently, I haven't run into any other issues besides the NETWORK_CONNECTION_UNAVAILABLE issue that I first posted about in the bug report. Brave just refuses to initiate sync when the phone is coming out of sleep. Is there a way to force sync? |
Well my current situation after battling with this issue on the desktop to a laptop for months, in my case is that I disabled sync. I rarely use my laptop these days and my phone is iOS and open tabs sync is non-existant. |
Why i can t send my Pages to a other Device? |
@MrGreenPro94 You can, it just takes a really long time the pages to get there. It can take anywhere from 1-3 minutes. |
@urbenlegend i use now a extensions as work arouns and it make it easier. I use Pocket |
@AlexeyBarabash Any progress on this bug? I am still seeing this issue on Android and it always delays sync by a few minutes whenever it happens. |
@urbenlegend no, unfortunately. I made another attempt today to reproduce it with Android <=> Windows devices chain, but no luck. |
Are you saying that it works for you even after a long period of not using the phone? I can only trigger the bug when I start using Brave after my phone has been sitting idle for a while. It seems like the sync service has a hard time resuming operation from an idle state. |
@urbenlegend , yes. |
@AlexeyBarabash Do you have battery optimization enabled or disabled for Brave? I am wondering if it has something to do with power management. |
@urbenlegend it is default, marked as
I believe when the app is not used, it gets terminated. |
I have this issue happening...always. The tab takes about a couple of minutes to "arrive" between devices. Every. Time. And, seeing that there are so many other people mentioning this, I wouldn't discard this issue so quickly. I'm on macOS and Android. Is there anything I can do to try to fix this on my end? Thanks! |
It happens to be slow regardless of what types of devices are involved. Even from desktop to desktop. |
Description
I've noticed that Brave on Android is frequently behind on sync updates and takes anywhere from 1-5 minutes after launching Brave before re-attempting sync. This makes sync features like
Send tab to device
andOpen Tabs Sync
almost unusable. This most frequently occurs after not using Brave for a few minutes or when the phone has been asleep for a while.When Brave is in this state,
chrome://sync-internals
reportsNETWORK_CONNECTION_UNAVAILABLE
with a retry time that is often before the current system time. See the screenshot belowSteps to reproduce
chrome://sync-internals
Actual result
Sending a tab to my Android device frequently takes anywhere from 1-5 minutes because of the issue in the screenshot below.
Expected result
Sending a tab to Android should trigger an immediate Sync update on my phone and show tab notifications. I should not have to browse to
chrome://sync-internals
and manually trigger an update. This is poor UX.Issue reproduces how often
Easily reproduced
Version/Channel Information:
Device details
Brave version
1.13.87
Website problems only
Additional information
I believe this is at the core of some of the other tab sync issues, like #10707
The text was updated successfully, but these errors were encountered: