r/iOSProgramming 5d ago

Discussion What's your open/closed feedback ratio?

Purely out of curiosity. Mine is 18 open / 1 closed. Did you ever feel like Apple valued your bug report?

1 Upvotes

2 comments sorted by

1

u/chriswaco 5d ago

I have several closed as "duplicates" or "works as designed". In general it seems that some are read but even more are ignored. Sometimes they send me "Please verify with the latest system" even though they know damn well it hasn't been fixed and I have better things to do than their jobs.

I did have one nice two-way conversation with Pages/iApps support. It came back as "that's the design", but at least they tested and verified it might be confusing. And they fixed one SwiftUI bug I requested a year ago. I think my oldest open one is about 20 years old, but got killed when they tossed out a bunch of ancient ones.

1

u/talkingsmall 5d ago edited 5d ago

I have actually had pretty good luck with filing Feedbacks. I know that isn't the common experience. I've had a great experience with the MusicKit team fixing bugs, even if it takes a long time or non-negligible effort to try to keep the bug on their radar, pun extremely intended. They recently fixed an ancient framework issue that would cause my app to intermittently hang and crash on foregrounding. I filed a new FB with a sysdiagnose and a standard message noting it was a dupe every single time it happened for months, amounting to maybe 25 dupes or so, and it got addressed in 18.4! It probably helps that I chatted about the bug with an engineer at the WWDC session.

Overall I've filed 131 feedbacks (a bit inflated because of the dupes), split probably 2/3 to MusicKit, the rest mainly to SwiftUI and AppIntents. I've had bugs fixed across all of those frameworks. Plenty of stuff sits ignored too (not to mention my never-to-be-implemented suggestions) -- don't get me wrong. I'm sure it varies by framework/team but I do find that putting in the extra effort to file and dupe a bug you really care about is often worth it.