3 ms·

I can offer some thoughts as to why this is the case: - Apple engineers are literally drowning in Radars. - Your F.A. Radar will arrive so late to an engineer

I can offer some thoughts as to why this is the case: - Apple engineers are literally drowning in Radars. - Your F.A. Radar will arrive so late to an engineer (after being filtered by QA) that the engineer is working on new features and marks F.A. bugs as low priority. - The iOS Simulator is a second class citizen.

giantrobot 4y ago
These are likely the exact issues. For the past several years for OS releases Apple sets priority deadlines. There's a date where all P1 bugs need to be closed/moved, and so on until near the scheduled release which is "zero bugs". All that means is bugs that didn't get fixed move into the next OS milestone. These deadlines basically preclude late breaking or low priority bugs to ever make an engineer's schedule. The only way is if an exec pushes on the bug or if it turns out to have higher impact than originally thought. Before Feedback Assistant bugs could come in from AppleCare support or developer relations. These could be some of the worst bugs to get assigned because they would be filled with extraneous details but not a crash or spin trace that would actually be useful.