Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

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 resposta
  • 8 têm este problema
  • 20 visualizações
  • Última resposta por 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 ?

Solução escolhida

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.

Ler esta resposta no contexto 👍 4

Todas as respostas (1)

chourmo51
chourmo51 Proprietário da pergunta
more options

Solução escolhida

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.