搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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.