Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

How to troubleshoot when logins do not synchronise after transfering Firefox for Android v54.0 from S6 to new S7, while history and bookmarks do sync?

  • 1 Antwort
  • 8 haben dieses Problem
  • 20 Aufrufe
  • Letzte Antwort von chourmo51

chourmo51
chourmo51
more options

I am changing smartphone from s6 to s7. I use Firefox for Android v54.0 and use the sync functionality mainly for sync Login and Bookmarks with my PC Version (current 54.0) and other devices. After loging in with my sync account on new smartphone, the logins will not synchronize, even after i remove the option "use master password". History or Bookmarks did and still do sync with other devices. Would you please have any troubleshoot steps for me ?

I am changing smartphone from s6 to s7. I use Firefox for Android v54.0 and use the sync functionality mainly for sync Login and Bookmarks with my PC Version (current 54.0) and other devices. After loging in with my sync account on new smartphone, the logins will not synchronize, even after i remove the option "use master password". History or Bookmarks did and still do sync with other devices. Would you please have any troubleshoot steps for me ?

Ausgewählte Lösung

OK. Today I did de-install Firefox for Android and reinstall it, connect Sync and now...logins were synx. So i assume the issue root cause has to do with the initial direct app transfer from S6 to S7 (per USB). KR.

Diese Antwort im Kontext lesen 👍 4

Alle Antworten (1)

chourmo51
chourmo51 Fragesteller
more options

Ausgewählte Lösung

OK. Today I did de-install Firefox for Android and reinstall it, connect Sync and now...logins were synx. So i assume the issue root cause has to do with the initial direct app transfer from S6 to S7 (per USB). KR.