I was the one who posted about this error message disappearing in 12.0 beta 6. Unfortunately shortly after, the error came back. I'm now on the 12.2 beta and the error is still there. Any chance for some engineering feedback here? This seems to be a wide-spread issue...

Thanks, this was very useful.