When Sync hits any error during JPAKE we show the message: "Firefox could not connect to Sync. Would you like to try again?" This will show if you bring up the sync screen and then just let it timeout (or if you are very slow entering your key on desktop). It would also show if you entered your key on desktop, but for some reason sync could not update your phone. Maybe we can provide a message that was a bit more descriptive, but applied in both situations. "Sync codes can not be verified" or something...
Marking 2.0next. We should show (a) a specific error message, and (b) a call to action for the user that describes how to resolve the issue or where to find more information.
tracking-fennec: --- → 2.0next+
Do we have support for this in Sync? Is this something we can do in Fennec?
Can we make some progress on this?
tracking-fennec: 6+ → 7+
Created attachment 540086 [details] [diff] [review] Patch Sorry. Been avoiding this because I'm not sure what the right answer is. On device we can detect a timeout and show a different message. This makes us write: "Your sync codes could not be verified. Would you like to try again?" as opposed to our normal cheery: "Fennec could not connect to Sync. Would you like to try again?" Try again and Manual Setup seem like the only two actions we would want to direct most users to (and Manual setup is kinda debateable). We could replace it with a link to SUMO. I will put up a second patch for that.
Attachment #540086 - Flags: review?(mark.finkle)
Created attachment 540087 [details] [diff] [review] Patch 2 - Help button Help button patch. Replaces "Manual Setup" button with "Get Help". Directs the user to https://support.mozilla.com/kb/Firefox%20Sync%20is%20not%20working
Attachment #540086 - Flags: review?(mark.finkle) → review+
Comment on attachment 540087 [details] [diff] [review] Patch 2 - Help button Code looks fine, but lets get a UI r+ before landing
Attachment #540087 - Flags: review?(mark.finkle) → review+
This is specifically a JPAKE error, and I don't want to start explaining JPAKE in these messages. We can probably do better here, but replacing manual setup isn't it, I think.
Let's just close this until we really have a good plan or need
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.