-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[Sync] GenerateCryptoErrorForTypes error, Sync isn't working #22898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
With the steps provided, at https://source.chromium.org/chromium/chromium/src/+/main:components/sync/nigori/nigori_sync_bridge_impl.cc;l=321?q=NigoriSyncBridgeImpl::NigoriSyncBridgeImpl&ss=chromium%2Fchromium%2Fsrc We provide the passphrase to make the decryption on normal sync setup flow. As for the broken sync setup flow I checked, whether it is enogh to make the same: So I am implementing to gave passphase supplied for such cases. |
As per brave/brave-ios#5304, iOS is also affected. |
When sync decryption passphrase is not set during sync setup, then sync goes into error state with bunch of GenerateCryptoErrorForTypes errors. This commit does set decryption passphrase for such cases. fixes brave/brave-browser#22898
When sync decryption passphrase is not set during sync setup, then sync goes into error state with bunch of GenerateCryptoErrorForTypes errors. This commit does set decryption passphrase for such cases. fixes brave/brave-browser#22898
We'll need some STR/Cases for Looks like it's working well on |
@kjozwiak , sure I have updated the issue head message with Thanks |
Removed |
Verification in progress with
Upgrade case - PASSEDFollowed steps from https://bravesoftware.slack.com/archives/CHGKGMHDJ/p1654603382608359?thread_ts=1654077649.892429&cid=CHGKGMHDJ, being sure that Reproduced the error with
Clean profile - PASSEDFollowed steps from https://bravesoftware.slack.com/archives/CHGKGMHDJ/p1654603382608359?thread_ts=1654077649.892429&cid=CHGKGMHDJ, being sure that Confirmed no error on ![]() Verification PASSED on
Upgrade case - PASSEDFollowed steps from https://bravesoftware.slack.com/archives/CHGKGMHDJ/p1654603382608359?thread_ts=1654077649.892429&cid=CHGKGMHDJ, being sure that Reproduced the error with
Clean profile - PASSEDFollowed steps from https://bravesoftware.slack.com/archives/CHGKGMHDJ/p1654603382608359?thread_ts=1654077649.892429&cid=CHGKGMHDJ, being sure that Confirmed no error on Verification passed on
Upgrade case - PASSEDFollowed steps from https://bravesoftware.slack.com/archives/CHGKGMHDJ/p1654603382608359?thread_ts=1654077649.892429&cid=CHGKGMHDJ, being sure that Reproduced the error with Clean profile - PASSEDFollowed steps from https://bravesoftware.slack.com/archives/CHGKGMHDJ/p1654603382608359?thread_ts=1654077649.892429&cid=CHGKGMHDJ, being sure that Confirmed no error on |
…t CR115 Fixes brave/brave-browser#30435 By default Brave enables Bookmarks datatype when sync is enabled. This caused DCHECK at DataTypeManagerImpl::DataTypeManagerImpl after OnEngineInitialized(true, false) call. ForcedSetDecryptionPassphrase test is intended to verify fix for brave/brave-browser#22898 and is about set encryption passphrase later setup after right after enabling sync, for example when internet connection is unstable. Related Prior to the mentioned below Chromium commit DataTypeManagerImpl wasn't created for bookmarks at ForcedSetDecryptionPassphrase test. Related Chromium change: https://source.chromium.org/chromium/chromium/src/+/3241d114b8036bb6d53931ba34b3bf819258c29d SyncServiceImpl::GetModelTypesForTransportOnlyMode(): Include NIGORI SyncServiceImpl::GetModelTypesForTransportOnlyMode() returns the set of types that are supported in transport-only mode. Before this CL, the returned set didn't include NIGORI (even though NIGORI *is* supported in transport-only mode). This had little practical impact, since NIGORI isn't configured along with other data types anyway - however, it *did* affect the "interested data types" for the purpose of invalidations. This CL special-cases NIGORI (or more precisely, ControlTypes()) in GetModelTypesForTransportOnlyMode(), similar to existing logic in SyncUserSettingsImpl::GetPreferredDataTypes(). This makes NIGORI part of the "interested data types" also in transport-only mode. Bug: 1358482 Change-Id: Ie7f4ff360ba98850869dfe8602e4bc8b86e8c9b0
…t CR115 Fixes brave/brave-browser#30435 By default Brave enables Bookmarks datatype when sync is enabled. This caused DCHECK at DataTypeManagerImpl::DataTypeManagerImpl after OnEngineInitialized(true, false) call. ForcedSetDecryptionPassphrase test is intended to verify fix for brave/brave-browser#22898 and is about set encryption passphrase later setup after right after enabling sync, for example when internet connection is unstable. Related Prior to the mentioned below Chromium commit DataTypeManagerImpl wasn't created for bookmarks at ForcedSetDecryptionPassphrase test. Related Chromium change: https://source.chromium.org/chromium/chromium/src/+/3241d114b8036bb6d53931ba34b3bf819258c29d SyncServiceImpl::GetModelTypesForTransportOnlyMode(): Include NIGORI SyncServiceImpl::GetModelTypesForTransportOnlyMode() returns the set of types that are supported in transport-only mode. Before this CL, the returned set didn't include NIGORI (even though NIGORI *is* supported in transport-only mode). This had little practical impact, since NIGORI isn't configured along with other data types anyway - however, it *did* affect the "interested data types" for the purpose of invalidations. This CL special-cases NIGORI (or more precisely, ControlTypes()) in GetModelTypesForTransportOnlyMode(), similar to existing logic in SyncUserSettingsImpl::GetPreferredDataTypes(). This makes NIGORI part of the "interested data types" also in transport-only mode. Bug: 1358482 Change-Id: Ie7f4ff360ba98850869dfe8602e4bc8b86e8c9b0
…t CR115 Fixes brave/brave-browser#30435 By default Brave enables Bookmarks datatype when sync is enabled. This caused DCHECK at DataTypeManagerImpl::DataTypeManagerImpl after OnEngineInitialized(true, false) call. ForcedSetDecryptionPassphrase test is intended to verify fix for brave/brave-browser#22898 and is about set encryption passphrase later setup after right after enabling sync, for example when internet connection is unstable. Related Prior to the mentioned below Chromium commit DataTypeManagerImpl wasn't created for bookmarks at ForcedSetDecryptionPassphrase test. Related Chromium change: https://source.chromium.org/chromium/chromium/src/+/3241d114b8036bb6d53931ba34b3bf819258c29d SyncServiceImpl::GetModelTypesForTransportOnlyMode(): Include NIGORI SyncServiceImpl::GetModelTypesForTransportOnlyMode() returns the set of types that are supported in transport-only mode. Before this CL, the returned set didn't include NIGORI (even though NIGORI *is* supported in transport-only mode). This had little practical impact, since NIGORI isn't configured along with other data types anyway - however, it *did* affect the "interested data types" for the purpose of invalidations. This CL special-cases NIGORI (or more precisely, ControlTypes()) in GetModelTypesForTransportOnlyMode(), similar to existing logic in SyncUserSettingsImpl::GetPreferredDataTypes(). This makes NIGORI part of the "interested data types" also in transport-only mode. Bug: 1358482 Change-Id: Ie7f4ff360ba98850869dfe8602e4bc8b86e8c9b0
…t CR115 Fixes brave/brave-browser#30435 By default Brave enables Bookmarks datatype when sync is enabled. This caused DCHECK at DataTypeManagerImpl::DataTypeManagerImpl after OnEngineInitialized(true, false) call. ForcedSetDecryptionPassphrase test is intended to verify fix for brave/brave-browser#22898 and is about set encryption passphrase later setup after right after enabling sync, for example when internet connection is unstable. Related Prior to the mentioned below Chromium commit DataTypeManagerImpl wasn't created for bookmarks at ForcedSetDecryptionPassphrase test. Related Chromium change: https://source.chromium.org/chromium/chromium/src/+/3241d114b8036bb6d53931ba34b3bf819258c29d SyncServiceImpl::GetModelTypesForTransportOnlyMode(): Include NIGORI SyncServiceImpl::GetModelTypesForTransportOnlyMode() returns the set of types that are supported in transport-only mode. Before this CL, the returned set didn't include NIGORI (even though NIGORI *is* supported in transport-only mode). This had little practical impact, since NIGORI isn't configured along with other data types anyway - however, it *did* affect the "interested data types" for the purpose of invalidations. This CL special-cases NIGORI (or more precisely, ControlTypes()) in GetModelTypesForTransportOnlyMode(), similar to existing logic in SyncUserSettingsImpl::GetPreferredDataTypes(). This makes NIGORI part of the "interested data types" also in transport-only mode. Bug: 1358482 Change-Id: Ie7f4ff360ba98850869dfe8602e4bc8b86e8c9b0
…t CR115 Fixes brave/brave-browser#30435 By default Brave enables Bookmarks datatype when sync is enabled. This caused DCHECK at DataTypeManagerImpl::DataTypeManagerImpl after OnEngineInitialized(true, false) call. ForcedSetDecryptionPassphrase test is intended to verify fix for brave/brave-browser#22898 and is about set encryption passphrase later setup after right after enabling sync, for example when internet connection is unstable. Related Prior to the mentioned below Chromium commit DataTypeManagerImpl wasn't created for bookmarks at ForcedSetDecryptionPassphrase test. Related Chromium change: https://source.chromium.org/chromium/chromium/src/+/3241d114b8036bb6d53931ba34b3bf819258c29d SyncServiceImpl::GetModelTypesForTransportOnlyMode(): Include NIGORI SyncServiceImpl::GetModelTypesForTransportOnlyMode() returns the set of types that are supported in transport-only mode. Before this CL, the returned set didn't include NIGORI (even though NIGORI *is* supported in transport-only mode). This had little practical impact, since NIGORI isn't configured along with other data types anyway - however, it *did* affect the "interested data types" for the purpose of invalidations. This CL special-cases NIGORI (or more precisely, ControlTypes()) in GetModelTypesForTransportOnlyMode(), similar to existing logic in SyncUserSettingsImpl::GetPreferredDataTypes(). This makes NIGORI part of the "interested data types" also in transport-only mode. Bug: 1358482 Change-Id: Ie7f4ff360ba98850869dfe8602e4bc8b86e8c9b0
Description
There are complains that on Android sometimes appears
Sync isn't working
popup and sync-internals contains GenerateCryptoErrorForTypes errors. Sync settings contains the controls with the placeholders for formatting.I could reproduce it by making actions with the local server.
Steps to reproduce
Actual result
GenerateCryptoErrorForTypes
errorsExpected result
No errors
Steps to reproduce if you can't run local sync server:
Actual:
the image on screen, and
GenerateCryptoErrorForTypes
in sync-internalsExpected:
sync works
Steps to reproduce if you can't run local sync server on Desktop, tested on
1.39.111
:Start new sync chain
=>Computer
=> copy code. Don't pressOK
, close the dialog instead.I have a sync code
Manage devices
sync screen. It is expected to have not devices in the list.GenerateCryptoErrorsForTypes
errorsIf then open page brave://settings/braveSync/setup then the sync state will be fixed by current UI settings page, but otherwise sync will be silently out of order.
Issue reproduces how often
Easily reproduced, but needs the local server and Android browser modification to be able connect the local server (hardcode local server ip)
Version/Channel Information:
Device details
Brave version
Website problems only
Additional information
The text was updated successfully, but these errors were encountered: