Interesting. Doesn't happen often that Apple would convey a simple solution that directly points to its fault. I guess the situation warrants their attention.I got it from a Slack I'm in, and the person who posted it got the info from their Apple System Engineer and was told they could share that info. I assume that it will be addressed in the 26.1 update, if not sooner.
