Closed
Bug 985744
Opened 11 years ago
Closed 11 years ago
Sync: cannot specify alternate server when pairing a device
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: shtrom, Unassigned)
Details
(Whiteboard: [bugday-20140324] Reporter asked for bug to be marked as invalid)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20140205 Firefox/24.0 Iceweasel/24.3.0 (Nightly/Aurora)
Build ID: 20140205091623
Steps to reproduce:
Having a devices already syncinc to an ownCloud server, I tried to sync a new device.
In the Sync settings tab of the device to be synced, I clicked “Pair a device”. I was given a set of number to enter into the other, already synced, device.
Actual results:
After I did, and a bit of waiting, both devices found each other (which I found odd considering the new one didn't even know which server to look for). They both declared the Sync successful.
However, the new machine never succeeded to sync. When troubleshooting (from the pop-up warning at the bottom of the window) I was taken to the Sync server status on the main server, rather than my ownCloud instance.
Expected results:
There should either be a way for paired devices to exchange information about where the Sync server is, or a text-box to enter its address as in the set up or sign-in without device.
| Reporter | ||
Comment 1•11 years ago
|
||
Nope, sorry. There was an issue with my ownCloud instance. I retried the pairing after fixing it, and it works.
The only issue is therefore to take people to the Mozilla Sync server status page in case of failure even if they are using an alternate server.
I suppose this bug should be closed as invalid, but I do not appear to have the rights to do so.
Comment 2•11 years ago
|
||
I'll close the bug for you. Have a good one!
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Updated•11 years ago
|
Whiteboard: [bugday-20140324] Reporter asked for bug to be marked as invalid
You need to log in
before you can comment on or make changes to this bug.
Description
•