Closed
Bug 576689
Opened 14 years ago
Closed 14 years ago
Fix Sync on Android Fennec
Categories
(Firefox :: Sync, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 576554
People
(Reporter: mwu, Assigned: mwu)
Details
(Keywords: regression)
Attachments
(1 file)
818 bytes,
patch
|
Details | Diff | Splinter Review |
Due to the combination of weave landing on m-c (causing weave to enter the omnijar) and data driven compreg landing, weave no longer works on Android Fennec.
Attachment #455811 -
Flags: review?(mconnor)
Comment 1•14 years ago
|
||
Comment on attachment 455811 [details] [diff] [review] Fix >- let uri = ioService.newURI("resource://gre/modules/services-sync", >+ let uri = ioService.newURI("resource://gre/modules/services-sync/", Why is that needed? Other than that, this duplicates stuff from bug 576554, but that's ok. We'll just have to sort that out during the next merge of fx-sync to m-c.
Assignee | ||
Comment 2•14 years ago
|
||
(In reply to comment #1) > (From update of attachment 455811 [details] [diff] [review]) > >- let uri = ioService.newURI("resource://gre/modules/services-sync", > >+ let uri = ioService.newURI("resource://gre/modules/services-sync/", > > Why is that needed? > I think the / is required when resolving something in a jaruri. It might be ok when dealing with a local file, but I suspect that without the /, something like resource://services-sync/asdf ends up like resource://gre/modules/services-syncasdf instead of resource://gre/modules/services-sync/asdf. I can check but things seem to break without this. It's also good for consistency since all the internal resource uri registration (for gre/gre-resources) uses a / at the end.
Comment 3•14 years ago
|
||
Fair enough! I've updated my patch for bug 576554 accordingly.
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•14 years ago
|
Attachment #455811 -
Flags: review?(mconnor)
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
•