Some of that work does benefit me: better understanding of the bug, verification that it’s not something I’m doing wrong, maybe some ideas of a workaround. I’v

Some of that work does benefit me: better understanding of the bug, verification that it’s not something I’m doing wrong, maybe some ideas of a workaround. I’ve stopped doing the second phase: packaging it up and submitting it to apple, because that’s shown itself to be an entirely negative experience. If apple’s not going to spend the $$ on internal QA, and they’re not going to spend the $$ on developer relations, I’m not especially interested in donating my time to help them. I know I’ve seen a similar sentiment from other developers for years. I think low quality / low content bug reports are usually worse than none, because they decrease the signal to noise ratio of bugs. Maybe if there was a better channel of communication, and I knew it’d be more interactive it’d be different.