I’m sorry, are you joking with this response? Let’s put this down to poor communication strategy, because I sincerely hope you’re not suggesting that confirmation is required that further action is necessary post-‘fix’?
The confirmation already exists in these forum posts alone. It would also exist if you jumped onto one of the multitudinous (and presumably, to a company with your resources, easily accessible) variations of machines reported as experiencing this error, and tried to do something as simple as a WQ.
There needs to be a catch-up implemented for affected users when (if?) this is fixed. Something simple enough to do would be to grant accounts using the Mac client the average % increase in cloak/AP for unaffected users during the Mac Lockout Period (as i’m referring to it).
If the average cloak increase for this Lockout was 3 levels, boost ours by 3 levels. If the average AP gain was, let’s say, 50k, boost us 50k. That way, those few who have been able to play on Mac during this time period will not receive undue benefit, or if they do it will be negligible. The rest of us will be in a position where, progression-wise, we’re not hamstrung (and therefore benched from M+/Raids and perpetually behind the curve) because of your incompetence.