I am not saying it is or it isn’t and I’m not saying Apple doesn’t ship bugs. I’m just saying that to simply decide it is because a relatively small group of people are having a problem is not a wise pursuit.
Do you know that Apple did not pre-announce changes? Do you know that every developer tested and corrected before Catalina 10.15.4 shipped? It is nearly impossible to test every combination of cables, hubs, docks, dingles, etc.,
On almost all, if not all OS updateS, many people experience problems of one sort or another. Having done Mac tech support for a living, most problems are beyond the control of Apple. If you saw my earlier post about my audio interface, you’ll note that the developer indicated testing for compatibility.
As noted, the vast majority are not seeing the issues seen here. If they were, it would be all over the news.
All that said, the process for identifying and fixing a problem involves working with all the parts and trying alternatives. If an alternative part works fine, what’s the conclusion? That Apple software targeted the part that doesn’t work? If a bunch of people started to complain about App A not working after an OS upgrade but the vast majority didn’t have any problem, do you think the problem lies with the upgrade, because that was the last change? I don’t think that makes any sense.
I’m telling you sometimes an OS upgrade reveals different problems. Sometimes they may be an Apple bug or simply a change that results in a new problem. It doesn’t really matter but if most folks aren’t having the problem, it is wise to look elsewhere too.
I can tell you this; every update reveals a bigger problem: people don’t backup. Nearly everyone here did not back up before installing the update, even though they were warned to do so. That is indeed a problem, and it is a user problem. Looking for scapegoats isn’t going to solve that.
And just because you report something before and after beta, doesn’t mean it’s actually an Apple bug. It’s better to see it merely as a problem looking for a solution. And the pool with the problem might be quite small.
All I’m trying to suggest is to be creative in understanding the problem instead of blaming the last introduced variable.