Closed Bug 1915532 Opened 2 months ago Closed 1 month ago

Password sync no longer working

Categories

(Fenix :: Accounts and Sync, defect)

Firefox 129
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: fzimmermann.pw, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:129.0) Gecko/20100101 Firefox/129.0
Firefox for Android

Steps to reproduce:

Passwords are no longer synced (approx since June) with Mobile Phone (Pixel 7, CalyxOS).
In Mull logout and pair again with Firefox on Desktop (Linux).
Installed Fennec and paired with Firefox on Desktop.
Desktop: Mozilla/5.0 (X11; Linux x86_64; rv:129.0) Gecko/20100101 Firefox/129.0
Fennec: Mozilla/5.0 (Android 14; Mobile; rv:129.0) Gecko/129.0 Firefox/129.0
Mull: Mozilla/5.0 (Android 10; Mobile; rv:129.0) Gecko/129.0 Firefox/129.0

Actual results:

Latest passwords are not synced with Firefox on Mobile Phone.

Expected results:

All passwords are synced.

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

Component: Untriaged → General
Product: Firefox → Fenix
Component: General → Accounts and Sync

Do you mean Fenix rather than Fennec?

Nope Fennec form Fdroid

It seems like you should be opening this bug on the non-mozilla browsers then, right?

Wasn't aware that Fennec isn't an official Mozilla build as everything, like the about section or description on Fdroid points to Mozilla.
Does it mean Mozilla does not provide an official build on Fdroid, which would be a shame?

The Fennec fdroid page says:

Fennec F-Droid is based on the latest Mozilla Firefox release. It has proprietary bits and telemetry removed, but still connects to various Mozilla > services that can track users.

The same reason they had to remove stuff is the same reason we can't put Firefox there. I'm really not an expert on this stuff and I doubt anyone who is will be reading this bug, but google has a number of hits asking about this.

I don't think there's anything actionable we can do here, so I'll close this, but feel free to reopen it if you think that's incorrect.

Status: UNCONFIRMED → RESOLVED
Closed: 1 month ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.