Apple randomly closes bug reports unless you "verify" the bug remains unfixed

Post by daheza » Thu, Mar 26, 2026, 4:01 AM UTC

nradov wrote: post #174

eob wrote: post #163

Earlier quoted context omitted.

My guess it's just the emergent behavior that results when a company doesn't provide developers time to fix bugs. If their week is already booked full just trying to keep up with the roadmap deadlines, a bug ticket feels like being tossed a 25lb weight when you're drowning. You could say: "but have pride in your work!" But if your company only values shipping, not fixing, that attitude doesn't make it through the fir…

What I've found to be most effective for program management is to set aside a maintenance team separate from the feature teams. The roadmap is then planned without counting anything for the maintenance team and they deal with bug tickets as they come in. Rotate the assignment periodically so that every developer has to occasionally spend a few months on the maintenance team.

Post by nradov » Thu, Mar 26, 2026, 4:05 AM UTC

arijun wrote: post #181

nradov wrote: post #177

Earlier quoted context omitted.

It's rather unreasonable to be annoyed. The maintainers may have entirely different priorities, which is fine. They're also likely being spammed with low-effort bug reports (not yours necessarily but from others). The great thing about open source projects you can just fix the bug yourself and submit a PR, or fork the whole project if the maintainers won't merge your changes. If you don't have the time or skills your…

> It's rather unreasonable to be annoyed. I disagree. If you discover that a bug that makes an open source library unusable to you, after spending time on learning and using that library, and the authors close the bug as a wontfix, I think being annoyed is quite reasonable, even expected.

Post by necovek » Thu, Mar 26, 2026, 4:10 AM UTC

what wrote: post #170

afdbcreid wrote: post #139

Earlier quoted context omitted.

I partially agree, but even with stalebots nobody is measuring the maintainers' productivity. So when they made the choice to use stalebots, they did that because they believe that's best for the project. It's different from corporate.

Nobody is measuring their productivity, but people definitely look at how many open issues they have and potentially how long those issues have existed. They’re likely incentivized to close issues for appearances.

Post by nullpoint420 » Thu, Mar 26, 2026, 4:13 AM UTC

twodave wrote: post #192

It’s quite possible (likely, even) for there to be more bugs reported than Apple has capacity to investigate. I assume this is just a filter they use to get the queue down to a more reasonable size and remove bug reports that are especially old (trusting that if they’re still issued they’ll be re-reported). This kind of culling happens all the time with low pri stuff and even sometimes medium pri if there’s a clear w…

Post by glitchc » Thu, Mar 26, 2026, 4:43 AM UTC

b112 wrote: post #96

Leherenn wrote: post #44

Earlier quoted context omitted.

From experience with Microsoft (paid) support (after doing 5 tickets because it's never the right team and apparently moving tickets internally is for losers), they will ask for proof of the reproduction. And they will take every opportunity to shift the blame ("Oh I can see in the log you're running an antivirus, open a ticket with them. Closed").

It'd kind of sad, how the market went. I suppose there are pluses too. But back in the 80s and 90s, margins were significantly higher. If you look at hardware, I recall selling hardware with 30% margin, if not more... even 80% on some items. Yet what came with that was support, support, support. And when you sell 5 computers a month, instead of 500, well.. you need that margin to even have a store. Which you need, be…