Sync throws fxa errors #653

Closed
opened 7 years ago by wolfbeast · 1 comments
wolfbeast commented 7 years ago (Migrated from github.com)

Even with fxa not enabled, it throws an error because the sync server doesn't support a request for fxa_credentials meta data that is still requested.

GET https://pmsync.palemoon.net/sync/index.php/1.1/{....}/storage/meta/fxa_credentials [HTTP/1.1 404 Not Found 339ms]

This is caused by the FxA migration code.

Even with fxa not enabled, it throws an error because the sync server doesn't support a request for fxa_credentials meta data that is still requested. ```` GET https://pmsync.palemoon.net/sync/index.php/1.1/{....}/storage/meta/fxa_credentials [HTTP/1.1 404 Not Found 339ms] ```` This is caused by the FxA migration code.
wolfbeast commented 7 years ago (Migrated from github.com)

Caused by the FxA Migrator module present in the Sync 1.40 client.
Part of this is resolved by 66eeafb but that still doesn't stop the errors at the end of synchronization.

Caused by the FxA Migrator module present in the Sync 1.40 client. Part of this is resolved by 66eeafb but that still doesn't stop the errors at the end of synchronization.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: MoonchildProductions/Pale-Moon#653
Loading…
There is no content yet.