No for me. I'm still goodIt seems that 17.5.1 has triggered a regression of this bug for me. Anyone else?
17.4 was fixed. Skipped 17.5, so I don't know if it was affected.
Uncertain whether WatchOS version may play a role; it affected 8.8.1 for me previously, and now 10.5 on a new watch. 10.4 seemed to be fine.
Same solution -- turning off the Watch, or killing the MDCrashReportTool process permits the sync to proceed as normal.
![]()
No for me. I'm still good