They may not really know either, as they might be waiting on Apple for some feedback.
There is the Win 10 precedent, where some symptoms of the problems were mentioned, but after a few weeks, some details were released about the problem being with MCSS, at a depth that only MS could know about from actually doing the investigation and discovering what was actually going on. And the problem was on their side.
MS is a little more transparent these days, and their audio team lead engages with the public too, as evidenced by their handling of an SD card issue recently, where the problem was purely on the device maker for using reserved bit fields in the file directory, but MS still implemented an extra check, and blogged about progress on the way, as well as on a GearSlutz thread. That still took a few weeks to come to fruition, just because some things take the time they take.
Now, if this one requires some investigation on Apple’s end, we have no idea how transparent they will really be to SB, let alone us.
I suppose it comes down to whether you just want to be told any old stuff when there is nothing to tell, or wait until something of consequence comes forth.