1918888 - tab sync is not working between devices, android and windows versions

Status: RESOLVED DUPLICATE of bug 1917989

(Firefox :: Sync, defect, P3)

Description

[jay21317]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:130.0) Gecko/20100101 Firefox/130.0
Firefox for Android

Steps to reproduce:

I just pushed sync now on both android and windows firefox

Actual results:

I can't see the tabs from firefox for android on windows, I can see windows tabs on android though

Expected results:

tabs should have shown up from android on windows.

Comment 1

[jay21317]

Attachment: sync log.rtf

here is the sync log

Comment 2

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Sync' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

[BugBot [:suhaib / :marco]]

The severity field is not set for this bug.
:markh, could you have a look please?

For more information, please visit BugBot documentation.

Comment 4

[Lina Butler (ex-Mozilla)]

Hi jay21317! The log you attached shows that you have a Primary Password configured—is that right? If so, Firefox will ask you to enter it at startup, but it's easy to miss that dialog (bug 1713862).

One more thing that would be helpful is to pull the logs from your Android device, to see what's happening in the Android-to-Desktop direction. The process for doing that is unfortunately a little advanced, but, if you're up for it, that would be super valuable for helping debug this.

Comment 5

[jay21317]

The primary password wasn't the issue, the cause was on the android phone, I ended up having to sign out and back in and it's been working since.

I also removed the devices from my Firefox account(I was seeing my cell listed twice)

Comment 6

[BugBot [:suhaib / :marco]]

The severity field is not set for this bug.
:markh, could you have a look please?

For more information, please visit BugBot documentation.

Comment 7

[Mark Hammond [:markh] [:mhammond]]

There are a few similar reports which I'm duping to bug 1917989 - for now I'll assume this is the same underlying problem.