Apple Watch co-sysdiagnose not generated in Family Setup / managed account scenario

Hi everyone,

I’m currently researching Apple Watch pairing behavior and diagnostic logging across different setup modes.

I can reliably trigger a co-sysdiagnose on an Apple Watch when it is paired in a normal standalone / standard configuration. In that case, the expected co-sysdiagnose archive appears on the paired iPhone.

However, in a Family Setup / managed account scenario, behavior is different:

The watch provides the expected haptic feedback after the sysdiagnose button combination But no co-sysdiagnose archive appears on the paired iPhone afterward The same hardware behaves differently depending on pairing/account configuration

My question is:

Is co-sysdiagnose collection, transport, or availability intentionally different for Family Setup / managed Apple Watch devices?

For example:

Are logs stored elsewhere? Is transfer to the organizer iPhone restricted? Is co-sysdiagnose unsupported in Family Setup mode? Are additional conditions required, such as Wi-Fi, charging state, unlocked devices, or a longer delay?

I may be missing something obvious, but I have not found documentation describing this difference. If this is expected behavior, I’d really appreciate a pointer to the relevant documentation.

Thanks a lot!

For debugging purpose, is there any chance that you can log in your Apple Watch and paired iPhone with an administrator account and see if that changes anything?

I am guessing that it is an intentional limit to prevent a managed device from leaking something in a sysdiagnose. You can start with filing a feedback report to see what the sysdiagnose folks have to say – If you do so, please share your report ID here. Thanks.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

Apple Watch co-sysdiagnose not generated in Family Setup / managed account scenario
 
 
Q