Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

Every time I restart my Firefox browser, my Sync information has gone and I need to re-set up Sync

  • 2 odpovede
  • 11 má tento problém
  • 5 zobrazení
  • Posledná odpoveď od wouna

more options

When I set up Sync using my sync key (via the "Set Up Sync..." option in the Firefox 5 menu), everything works fine and all of my data is synced. However, when I close my browser and re-open it, the "Set Up Sync..." now reappears and the browser is no-longer synced.

Any ideas?

When I set up Sync using my sync key (via the "Set Up Sync..." option in the Firefox 5 menu), everything works fine and all of my data is synced. However, when I close my browser and re-open it, the "Set Up Sync..." now reappears and the browser is no-longer synced. Any ideas?

Vybrané riešenie

Hi wouna,

If you have configured your browser to clean up the browsing history after closing the browser, the Sync configuration is also erased. This is something known and will be solved in the future.

In the meantime you can tell Firefox to remember your configuration after closing in the custom configuration of your privacy settings.

I hope it helps.

Čítať túto odpoveď v kontexte 👍 5

Všetky odpovede (2)

more options

Vybrané riešenie

Hi wouna,

If you have configured your browser to clean up the browsing history after closing the browser, the Sync configuration is also erased. This is something known and will be solved in the future.

In the meantime you can tell Firefox to remember your configuration after closing in the custom configuration of your privacy settings.

I hope it helps.

more options

Of course! That makes sense if weave stores the passwords in the password manager. The 'bug' also occurs, it seems, if you have permanent private browsing mode enabled; although, in my opinion, it's not so much a 'bug' as this behaviour is to be expected when you think about it.

Thanks for the tip!