Not my tickets specifically. I don't think they're out to get me individually. On the contrary, this is a common practice, which affects many developers. I just happen to be relatively loud, as far as blogging is concerned.

▲

CoolGuySteve 2 hours ago | parent [-]

Yes I understand that. ~50000 engineers aren't conspiring to close all tickets that way. It's a stupid line of thinking.

More than likely your steps to reproduce are too laborious to receive attention relative to the value fixing the bug would provide. That's why they're asking you to verify it still happens. Seems pretty simple right?

There's also a strong chance your ticket was linked as a duplicate of some other issue that was fixed in the beta and they want you to verify that's the case but they won't expose their internal issue to you for a variety of reasons.

	▲	lapcat an hour ago \| parent [-]
		> ~50000 engineers aren't conspiring to close all tickets that way. I didn't say that either. It's happened to me only sporadically, but multiple times. I agree with you that teams within Apple manage their own tickets. Perhaps some individual teams are declaring bug bankruptcy at some point, so only their bugs would go out for verification. I don't really know. I wish I did. What I do know is that multiple teams have done this at different points. There's indisputably a company-wide DevBugs canned response for this. It's the same exact language every time. You can even Google it. > It's a stupid line of thinking. Please respect the HN guidelines: https://news.ycombinator.com/newsguidelines.html > More than likely your steps to reproduce are too laborious to receive attention. That's why they're asking you to do it. It was much more laborious for me, because I do not install the macOS betas. > Seems pretty simple right? No, it doesn't explain why specifically, after 3 years, they were suddenly asking me to verify with macOS 26.4 beta 4.