Broadly speaking, there are two questions to ask when a bug is found in software:
(1) What are the specific parameters of this bug?
(2) Why is this bug able to exist in the first place?
Obviously, #2 is broad and philosophical, and you can waste a lot of time and effort on it even before it comes to the potentially large time and effort it'll fix to address it meaningfully with actual code changes. But if you only ever ask question #1, you'll often only fix symptoms of fundamental problems in the approaches used; conversely, if you ask (and can find a real answer to) question #2, you can prevent future bugs and fix ones you don't even know about yet. It may cost you time and effort in the short term, but it can potentially save a LOT of time and effort in the long term.
Apple seems to do a really bad job at approaching things from a perspective of fixing fundamental problems rather than just putting out fires as they appear, particularly considering the ungodly amount of money they have and thus potential resources to throw at such concerns. I mean, when the problem *last* month came up I went "haha, really, again?!" because *that* was far from the first time essentially the same problem has come up across their software.