Open Bug 1794224 Opened 3 years ago Updated 3 years ago

Possibly incorrect handling of persisted engine state during closely spaced, subsequent syncs

Categories

(Firefox for Android :: Accounts and Sync, task)

All
Android
task

Tracking

()

People

(Reporter: jonalmeida, Unassigned)

Details

From github: https://github.com/mozilla-mobile/android-components/issues/7874.

Splitting from https://github.com/mozilla-mobile/android-components/issues/7335, in which @mhammond notes:

I believe that the persisted state for syncing was fetched at the time the sync call was queued, not when it was executed. So if there's one sync running and one sync queued, and the first sync changes (say) the declined engines, it seems likely that second sync will execute with the old state, not new state as updated by that first sync.

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Severity: -- → N/A
Type: defect → task
You need to log in before you can comment on or make changes to this bug.