搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

New Firefox Sync can't proceed beyond verification link

  • 4 回覆
  • 10 有這個問題
  • 1 次檢視
  • 最近回覆由 YellowApple

more options

Verification emails are received successfully, but the link to confirm my email address consistently results in a "Verification link damaged" page, regardless of whether I click on the link, manually copy/paste it, etc. This is preventing me from successfully creating a Firefox Sync account.

Verification emails are received successfully, but the link to confirm my email address consistently results in a "Verification link damaged" page, regardless of whether I click on the link, manually copy/paste it, etc. This is preventing me from successfully creating a Firefox Sync account.

被選擇的解決方法

YellowApple, For the new version of sync the version of Firefox would need to to be the same. On version 29 for Desktop the new sync account should work. The verification looks ok, and it sounds like it is syncing.

從原來的回覆中察看解決方案 👍 0

所有回覆 (4)

more options

if you take out the hash tag and verification code, can you paste the example of the link you received? you can pm it to me too and we can check with the cloud services team to see what happened?

more options

Well, the verification went through now, but signing in to Firefox Sync now fails with a message unhelpfully stating "Could not sign in". This only seems to be happening on Firefox for Android, however; sign-in works fine on my desktop running Firefox 24.

由 YellowApple 於 修改

more options

選擇的解決方法

YellowApple, For the new version of sync the version of Firefox would need to to be the same. On version 29 for Desktop the new sync account should work. The verification looks ok, and it sounds like it is syncing.

more options

Right, but the issue (as I said) is currently with Firefox for Android (latest version from Play Store), which at that point was returning a "Could not sign in" error, and now is simply crashing whenever I attempt to access the "Sync" settings option.

Whatever the case, the original issue (regarding verification failing) seems to be resolved now. I'll just fiddle with the mobile app and see if I can get it to behave properly. Thanks.