Comment by kccqzy
8 hours ago
Did you read the bug report? This is not your garden variety THIS IS BROKEN YOU SUCK FIX THIS bug. It is respectful, it has a minimal reproducer, and it is communicated clearly. There’s no reason to stall it using the sysdiagnose requirement.
And yes, this is not the first time I’ve seen Apple requiring sysdiagnose for an excellently written report. Even John Siracusa would get these sysdiagnose requests; it’s a stalling tactic being applied indiscriminately.
If Apple cannot distinguish between an angry nontechnical user that SHOUTS IN UPPERCASE and a developer that communicates professionally with an equal, that’s Apple’s problem.
Especially since sysdiagnose contain so much info, it’s bad opsec to give that info over. Unless you repro in a fresh VM maybe.
Because you're testing pre-release software on a dedicated machine... right?
The distinction doesn’t really matter. Apple will ask for a pointless sysdiagnose even when one reports bugs in released software.
You've convinced yourself that asking for a sysdiagnose is only ever used as a stalling tactic by Apple. There's not much I can say that will change your mind.
A minimal reproduction is great in a bug report but it's still not a complete in-situ snapshot of the machine.