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.
Re:macOS 15.8.2 Breaks OpenGL
by simondotau on Monday October 19, 2026 @04:16AM
(#50149722)
It’s not pointless when it allows an Apple developer to rapidly mimic the exact environment, in case it’s an extremely narrow bug involving a second-supplier controller chip.
It's usually pointless. I attach very few sysdiagnoses to my bug reports.
Re:macOS 15.8.2 Breaks OpenGL
by giantrobot on Sunday October 18, 2026 @08:44PM
(#50147045)
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.
I didn’t say sysdiagnose is only used as a stalling tactic. It may be useful if the reporter’s minimal reproducer doesn’t reproduce. But requiring it indiscriminately is definitely a stalling tactic.
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.