It appears to me, that the error has resurfaced in Xcode 13 betas 1 and 2. Has anyone else experienced that?