Sync: failed DCHECK when delete device record arrives twice
See original GitHub issueDescription
If two delete device records arrives to sync service, there is a failed DCHECK
[83053:775:0103/160933.609992:FATAL:sync_devices.cc(175)] Check failed: existing_it != std::end(devices_).
https://github.com/brave/brave-core/pull/1193#issuecomment-451308001
Steps to Reproduce
No steps to reproduce for QA, because this appears on debug builds only. Could be reproduced with a related PR unit-test.
Brave version (brave://version info)
Version 0.61.0 Chromium: 72.0.3626.28 (Developer Build) (64-bit)
Reproducible on current release:
- Does it reproduce on brave-browser dev/beta builds? no
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Fix email sync issues or remove a device from your Outlook on ...
> View all Outlook settings > General > Mobile devices. Select your device in the list, and then select Delete to delete the...
Read more >Troubleshooting weird Azure AD Join issues - ITProMentor
DeviceAuthStatus : FAILED. Device is either disabled or deleted. As well, you will not find the object in the Azure AD devices list, ......
Read more >The Most Common Annoying iTunes 12 Sync Issues and ...
Open the Music app to check. Instead of seeing the same song twice, you should see a cloud icon, which indicates you can...
Read more >SYNC™ Troubleshooting
Try deleting your device from SYNC and deleting SYNC from your device, then trying again. Always check the security and auto accept prompt...
Read more >How to Resolve Duplicate Outlook for iOS Contacts
Microsoft is working with Apple to resolve why errors occur, especially in synchronization of Outlook contacts from iCloud to multiple devices.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks @rebron @kjozwiak , just had set the correct milestones.
@kjozwiak correct, this issue cannot negatively affect users on production, this appears only in debug builds. This is not going to cause issues when users are removing devices.