Closed Bug 1684405 Opened 5 years ago Closed 5 years ago

Creating a new login should cause a sync

Categories

(Firefox :: Sync, defect)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: jrmuizel, Unassigned, NeedInfo)

Details

After creating a new login I had to manually sync before the login would show up in Firefox Lockwise on my phone. This was not the behaviour I expected and I hunted around for a while to figure out why the new login was not showing up.

I think this should already happen, perhaps not immediately but very soon on the next sync. https://searchfox.org/mozilla-central/rev/809ac3660845fef6faf18ec210232fdadc0f1ad9/services/sync/modules/engines/passwords.js#455,460,483-495 Mark can probably give more specifics.

Flags: needinfo?(markh)

Hi Matt!

Jeff: Matt is correct - we should sync immediately after adding a new login. The only exception to this might be if the password is added within 10-20 seconds of the browser starting up (I opened bug 1685014 for that case) - but in that case a manual sync probably will also not work as sync will not know the login has changed.

If you are able to reproduce this, Sync does keep some logs which may help us find the problem. Instructions for how to locate and attach the logs can be found at https://wiki.mozilla.org/CloudServices/Sync/File_a_desktop_bug - and in particular, follow the instructions for enabling "success" logs, then reproduce your issue (eg, create a new login after waiting 30 seconds or so), and attach any new logs which then appear.

Flags: needinfo?(markh) → needinfo?(jmuizelaar)

Moving this to the sync component as I don't think there is anything we can fix from the about:logins / password manager side.

Component: about:logins → Sync

Thanks again for reporting this issue, but we are unable to determine the cause of the problem without the requested information. If you are able to provide this information, please just add a comment in this bug with that information and we'll get back to you as soon as we can, but in the meantime we are closing this bug so we can focus on the issues which we can address.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.