Forum Discussion
Dev 75.0.139.1 Broke Sync
Hi, thanks for reporting the issue! In order to effectively debug the sync issue, would you please file a feedback (via the smiley face) to help us gather sync diagnostic log? Please add "[tomscharbach]" in the description field and we'll get back to you when we have more details to share. Thanks!
Hi, thanks for reporting the issue! In order to effectively debug the sync issue, would you please file a feedback (via the smiley face) to help us gather sync diagnostic log? Please add "[tomscharbach]" in the description field and we'll get back to you when we have more details to share. Thanks!
Joon Chang Yes, I will report it through Feedback, and I will also open a Microsoft Edge ticket.
I don't trust Feedback that much when it comes to tracking down bugs, since I reported a syncing issue (with a careful log) regarding interaction between Edge Classic sync and Edge Chromium sync (BUG 21314632), and got an "all fixed" message from Feedback while getting numerous "we are working on it, involving several teams" from the MES lead.
However, since this is a known issue (based on the number of comments regarding issues in the most recent builds of Canary, I would appreciate it if you would look up the MES ticket (and bug number) for those builds, and add this to the pile. The issue is almost certainly inherited from an unresolved issue in the last few Canary builds.
tomscharbach I've checked Bug 21314632 and it has not been fixed yet. I'll wait for your feedback (sync log) so we can effectively investigate the latest sync issue.
Joon Chang It took me a long time to figure this out but I think that the issue I reported was related to corruption of my MSA and related accounts that occurred during or immediately after Edge Chromium was updated. I discovered the corruption almost by accident, but after I cleaned out every bit of browser stored data, and stored temporary data on the computer, then restarted and reconnected, the sync issue resolved and has no occurred again over 24 hours of additional testing. Please see the attached log.
