ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mozilla Sync not working with SeaMonkey after getting the new Sync.

  • 6 ردود
  • 17 have this problem
  • 1423 views
  • آخر ردّ كتبه skierpage

more options

When I try to pair my SeaMonkey browser to Firefox Sync (Mozilla Sync) it does not work.

Tried these steps and it does not sync:

http://www.seamonkey-project.org/doc/sync

الحل المُختار

You would have to install a Firefox 28 version and connect to the old Sync account. Then you can update again to Firefox 30.

Read this answer in context 👍 1

All Replies (6)

more options

Starting with FF29, a new version of Sync has been introduced which uses Firefox accounts. https://support.mozilla.org/en-US/kb/how-do-i-set-up-firefox-sync

Seamonkey hasn't adopted the new Sync yet. So you cannot set up a new Sync account or pair a device anymore (bug 998807). Workaround: Use an older version of SeaMonkey for such tasks for now.

Modified by christ1

more options

I have already updated to the new Mozilla sync, now my SeaMonkey will not sync to my existing account, any way to get it to do so?

more options

I guess you'll have to wait until Seamonkey implements the new sync.

You could also go back to the old sync on all devices, but that would be a big hassle and not recommended.

more options

I will just have to be disappointed for a bit... Thanks for your help Christ1.

more options

الحل المُختار

You would have to install a Firefox 28 version and connect to the old Sync account. Then you can update again to Firefox 30.

more options

bug 1022319 is for SeaMonkey to support the new Sync. If you're trying to sync SeaMonkey with Firefox for Android or the latest Firefox, you are out of luck.

I requested that the support article on updating to Firefox sync mention that SeaMonkey doesn't work, and filed bug 1078092 that http://www.seamonkey-project.org/doc/sync should mention this bug.

Modified by skierpage