Closed Bug 1210362 Opened 4 years ago Closed 4 years ago
"sign in to sync" "Cookies are still disabled" although the are not
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; Touch; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; Tablet PC 2.0; rv:11.0) like Gecko Steps to reproduce: Tools -> Set up sync... -> button "Get started" Actual results: Message: "Please enable cookies ..." -> button "Try again" -> Message: "Cookies are still disabled". (and sync doesn't start. But cookies ARE enabled. Moreover I allowed cookies for accounts.firefox.com (see attached screen shots). I saw some similar issue descriptions but I didn't see any true solution nor contributory answer. Expected results: Synchronization.
Component: Untriaged → Sync
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Thanks for the report. The error message is slightly misleading here in that both cookies and localStorage are required. I suspect that your combination of settings may be allowing cookies but not localStorage. /cc :vladikoff who's my go-to expert on these things...Vlad, have you seen this situation before?
Component: Sync → Server: Firefox Accounts
Product: Firefox → Cloud Services
Version: 41 Branch → unspecified
For example, do you have dom.storage.enabled preffed off?  http://kb.mozillazine.org/Dom.storage.enabled
Indeed my dom.storage.enabled parameter was set to "False". By reverting it to "True" then I access to my account and I can launch the sync. Thank you very much Ryan. But I wonder what could happen if I can't control dom.storage on my computer. It seems to me to be risky. Besides, the procedure to sync is heavy. You have to connect to your account first, you receive an "Account activity notice" and so on. j-p
Happy this was resolved! :rfkelly let me know if we should also check for localStorage and improve our messaging on this in the future.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
YES please ! Improve your messaging. With the current message the user spends a lot of time checking what could be wrong with his cookies. That's what happened to me.
Yep, we should definitely iterate on the messaging here, I filed  to track that work.  https://github.com/mozilla/fxa-content-server/issues/3129
You need to log in before you can comment on or make changes to this bug.