Closed
Bug 911118
Opened 11 years ago
Closed 11 years ago
Cannot synchronize with my android client
Categories
(Firefox :: Sync, defect)
Firefox
Sync
Tracking
()
RESOLVED
DUPLICATE
of bug 756763
People
(Reporter: ggarbhad, Unassigned)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release)
Build ID: 20130814063812
Steps to reproduce:
I set up my own sync server at home following this howto:
http://docs.services.mozilla.com/howtos/run-sync.html
I installed the latest version
I managed to sync all my desktop clients.
Yet I cannot get it to work my Android phone. I'm using current stable version in Google Play (Firefox 23.0).
Actual results:
Got to Settings -> Sync -> Advanced Setup...
I fill all the input fields, select custom server and input my host's URL. Then I press "Connect".
Firefox tries to connect and then brings me back to the same screen, all fields still filled with my data, as if nothing happenned. No error message.
On my web server, I see this on the access logs (source IP removed):
XX.XX.XX.XX - - [30/Aug/2013:11:53:24 +0200] "-" 400 0 "-" "-"
XX.XX.XX.XX - - [30/Aug/2013:11:53:25 +0200] "-" 400 0 "-" "-"
Expected results:
It should have started the sync process as with any of my desktop clients :)
Reporter | ||
Comment 1•11 years ago
|
||
By "I installed the latest version" I meant that I'm running the sync server from mercurial, as specified on the link above and update it periodically.
My phone is a Google Galaxy Nexus, with latest stable CyanogenMod (10.1.2), which is based on Android 4.2.2.
Reporter | ||
Comment 2•11 years ago
|
||
I just came across this:
http://160.twinql.com/how-to-file-a-good-android-sync-bug/
I'm attaching the output of adb logcat.
Reporter | ||
Comment 3•11 years ago
|
||
Reporter | ||
Updated•11 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•6 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•