Closed vasilicatamas closed 4 years ago
Looks like the error in the attached text file is related to extension-storage:
1585141508810 Sync.Status DEBUG Status for engine extension-storage: error.engine.reason.unknown_fail 1585141508811 Sync.Status DEBUG Status.service: success.status_ok => error.sync.failed_partial 1585141508811 Sync.ErrorHandler DEBUG extension-storage failed: Error: HTTP 401 Unauthorized: Missing Authorization Token (Please authenticate yourself to use this endpoint.)(resource://services-common/kinto-http-client.js:2771:5) JS Stack trace: ServerResponse@kinto-http-client.js:2771:5 processResponse@kinto-http-client.js:2925:13
I believe this is a known error and is related to the kinto issues.
On Wed, Mar 25, 2020 at 9:37 AM Vasilica Tamas notifications@github.com wrote:
Build: Stage
Affected platforms: Windows 10
Prerequisites: Set identity.fxaccounts.autoconfig.uri to https://accounts.stage.mozaws.net and services.sync.log.appender.file.logOnSuccess to true
Steps to reproduce:
- Login on 2 Firefox profiles using the following testing account large@sharklasers.com - sync ID 5752141
- On first profile spend some time to create some new browsing data.
- Perform a Sync Now on the first profile.
- Trigger a Sync Now on the second profile.
Expected results: All the new data created while browsing on the first profile is successfully synced on profile B without encountering any errors.
Actual Results: All the new data from the first profile is synced on the second profile but only error files are displayed in about:sync-log.
I am attaching a sync error file: syncerror.txt https://github.com/mozilla-services/services-engineering/files/4382164/syncerror.txt
[image: syncerrors] https://user-images.githubusercontent.com/18114210/77561428-59102900-6ec7-11ea-9b36-4d5fd0bdc956.gif
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mozilla-services/services-engineering/issues/43, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAIXKYKVTVBYF4XVGJIYY3RJIXLFANCNFSM4LTSYF7Q .
I don't think the storage.sync URL is provided by the autoconfig stuff. I think you may have to set webextensions.storage.sync.serverURL
to https://webextensions-settings.stage.mozaws.net/v1
.
I don't think the storage.sync URL is provided by the autoconfig stuff. I think you may have to set
webextensions.storage.sync.serverURL
tohttps://webextensions-settings.stage.mozaws.net/v1
.
I confirm that after setting this pref the sync errors have disappeared.
Build: Stage
Affected platforms: Windows 10
Prerequisites: Set identity.fxaccounts.autoconfig.uri to https://accounts.stage.mozaws.net and services.sync.log.appender.file.logOnSuccess to true
Steps to reproduce:
Expected results: All the new data created while browsing on the first profile is successfully synced on profile B without encountering any errors.
Actual Results: All the new data from the first profile is synced on the second profile but only error files are displayed in about:sync-log.
I am attaching a sync error file: syncerror.txt