Fix broken startup sync-lock
## Issue
In 38c13cf5
, an additional `doGetAndPopulatePreferences` was added in `doSignIn` to ensure we have populated the preferences at least once. With that, `doHandleSyncComplete` can skip `doGetAndPopulatePreferences` is there is no change in the hash.
The addition broke the "initial sync lock", thus incorrectly allowing users to change preferences when the process is not completed.
## Change
I think the additional call is no longer needed since we now store a local hash for comparison, so `doGetAndPopulatePreferences` wouldn't be incorrectly skipped in the first ever `doHandleSyncComplete`.
This commit is contained in:
parent
2ea37e7708
commit
b6d21692e6
1 changed files with 0 additions and 1 deletions
|
@ -531,7 +531,6 @@ export function doSignIn() {
|
|||
pushNotifications.validate(user.id);
|
||||
}
|
||||
|
||||
dispatch(doGetAndPopulatePreferences());
|
||||
dispatch(doNotificationSocketConnect(true));
|
||||
dispatch(doNotificationList(null, false));
|
||||
dispatch(doCheckPendingClaims());
|
||||
|
|
Loading…
Reference in a new issue