Closed
Bug 1093915
Opened 10 years ago
Closed 7 years ago
(Nightly 36.0a1) Sync is buggy on my desktop and shows a blank page when logging in.
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ramgowda2012, Assigned: stomlinson)
References
Details
Attachments
(1 file)
26.90 KB,
image/jpeg
|
Details |
User Agent: Mozilla/5.0 (Android; Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 Build ID: 20141104030202 Steps to reproduce: I tried to log into an sync account on Nightly 36.0a1 (32 bit) on windows 7 (x64) (had to buy a new computer) I had gone to settings, then sync, then log in, switched to the and I was confused why it failed to show anything for the 3 minutes I staired at the computer. Actual results: The page did not load, even without addons enabled (none were downloaded) and a fresh new profile was created and all cookies were cleared shortly after and I reloaded the page (to no success). I received no errors of any kind or any message or even an e-mail. The console never reported anything wrong. Expected results: I should have gotten at least a warning or error of some kind telling me that something went wrong. When I logged in to my sync account on my android phone (nightly 36.0a1), it had worked.
Updated•10 years ago
|
Component: Server: Sync → Firefox Sync: Backend
Comment 2•10 years ago
|
||
Likely to be an issue with the content server (issues are generally tracked here: https://github.com/mozilla/fxa-content-server/issues/).] Without any console errors or anything this will be hard to debug. Can you still reproduce this?
Component: Firefox Sync: Backend → Server: Sync
Flags: needinfo?(ramgowda2012)
Reporter | ||
Comment 3•10 years ago
|
||
(In reply to :Gavin Sharp [email: gavin@gavinsharp.com] from comment #2) > Likely to be an issue with the content server (issues are generally tracked > here: https://github.com/mozilla/fxa-content-server/issues/).] > > Without any console errors or anything this will be hard to debug. Can you > still reproduce this? Im not sure I can reproduce it on another computer
Reporter | ||
Comment 4•10 years ago
|
||
(In reply to :Gavin Sharp [email: gavin@gavinsharp.com] from comment #2) > Likely to be an issue with the content server (issues are generally tracked > here: https://github.com/mozilla/fxa-content-server/issues/).] > > Without any console errors or anything this will be hard to debug. Can you > still reproduce this? The only errors I found is 20:49:34.098 Unknown pseudo-class or pseudo-element '-webkit-search-cancel-button'. Ruleset ignored due to bad selector. normalize.css:366 20:49:34.098 Error in parsing value for 'min-height'. Declaration dropped. main.css:125 20:49:34.098 Expected media feature name but found 'min-device-pixel-ratio'. main.css:144 20:49:41.606 Unknown property 'speak'. Declaration dropped. ed4a4420.en_US.css:1 20:49:41.607 Expected 'none', URL, or filter function but found 'progid'. Error in parsing value for 'filter'. Declaration dropped. ed4a4420.en_US.css:1 20:49:41.607 Unknown pseudo-class or pseudo-element '-ms-input-placeholder'. Ruleset ignored due to bad selector. ed4a4420.en_US.css:1 20:49:41.607 Unknown property 'appearance'. Declaration dropped. ed4a4420.en_US.css:1 20:49:41.607 Unknown property 'user-select'. Declaration dropped. ed4a4420.en_US.css:1 20:49:41.607 Unknown pseudo-class or pseudo-element '-ms-value'. Ruleset ignored due to bad selector. ed4a4420.en_US.css:1 20:49:41.608 Expected media feature name but found '-webkit-min-device-pixel-ratio'. ed4a4420.en_US.css:1 20:49:41.608 Expected media feature name but found '-moz-min-device-pixel-ratio'. ed4a4420.en_US.css:1 20:49:41.608 Expected media feature name but found '-o-min-device-pixel-ratio'. ed4a4420.en_US.css:1 20:49:41.608 Expected media feature name but found 'min-device-pixel-ratio'. ed4a4420.en_US.css:1 20:49:44.370 TypeError: t is null 1da513a8.main.js:14 20:49:57.077 The Web Console logging API (console.log, console.info, console.warn, console.error) has been disabled by a script on this page.
Reporter | ||
Comment 5•10 years ago
|
||
Firefox nightly crashed when I tryed to check the back end, then I checked the crash logs and found it was deleted. The console did stay open while I copyed it.
Comment 6•10 years ago
|
||
What is the setting of `dom.storage.enabled` in about:config?
Reporter | ||
Comment 7•10 years ago
|
||
It is false but is default for some reason, every other update had it as true and default.
Flags: needinfo?(ramgowda2012)
Reporter | ||
Comment 8•10 years ago
|
||
It is false but is default for some reason, every other update had it as true and default.
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(ramgowda2012)
Reporter | ||
Comment 9•10 years ago
|
||
It had showed the sync screen and I logged in. after trying to login It said my sync was outdated. Even when Firefox nightly was up to date and the other devices connected to sync was also up to date.
Flags: needinfo?(ramgowda2012)
Reporter | ||
Comment 10•10 years ago
|
||
I had the ability to receive bookmarks and everything else but my bookmarks from the computer did not go through.
Reporter | ||
Comment 11•10 years ago
|
||
*to the computer
Reporter | ||
Comment 12•10 years ago
|
||
The original problem was fixed after rebooting the computer. only bookmarks are failing to be transferred through and still work.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Comment 13•10 years ago
|
||
Issue in github to track the 't is null' error and blank UI - https://github.com/mozilla/fxa-content-server/issues/1848
Assignee | ||
Comment 14•10 years ago
|
||
Re-opening until I properly fix this.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WORKSFORME → ---
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → stomlinson
Assignee | ||
Comment 15•7 years ago
|
||
I have not seen any more reports of this being a problem. Closing as fixed.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 7 years ago
Resolution: --- → FIXED
Updated•1 year ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•