Pairing failing with 500 errors
Categories
(Cloud Services :: Server: Firefox Accounts, defect)
Tracking
(Not tracked)
People
(Reporter: pierre.vanespen, Unassigned)
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:130.0) Gecko/20100101 Firefox/130.0
Firefox for Android
Steps to reproduce:
I tried to syncronize firefox on my phone with firefox on my laptop. I scanned the QR code.
Actual results:
The I got an 500 error message.
Expected results:
Syncronization of Firefox on both my devices.
Comment 3•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Sync' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 4•1 year ago
|
||
Hi Pierre!
Thank you for bringing this issue to our attention. We experienced some intermittent server issues yesterday, which have since been resolved. Could you please try again and let us know if the problem persists?
Thank you for your patience!
I've just tried another time, without success. Same problem, with "500 error" message.
Updated•1 year ago
|
Comment 6•1 year ago
|
||
That's very odd but almost certainly remains a server problem - does it still reproduce?
Yes, unfortunately it still does reproduce.
Comment 8•1 year ago
|
||
Thanks for getting back to us - best I can tell, the desktop Firefox is connected correctly and syncing, but the process of pairing the Android device is what's failing. Hopefully the server team can offer more insights.
Comment 9•1 year ago
|
||
@maria - are you able to reproduce this?
@pierre - in your "Mozilla bug.png" screenshot there is a little arrow next to the text. If you click it it will show a more detailed error message. Is it possible to send us that? Alternatively, looking at the developer console in Firefox could also show the error message.
Comment 10•1 year ago
|
||
Hello @Wil, Apologies for the late reply on this.
I have tried the pair flow on Android using Tain prod & stage with the latest Firefox release and Firefox 130, but I couldn't reproduce the issue.
Updated•1 year ago
|
Description
•