Last tested: May 6, 2020
This error occurs when, for example, we have project import where Project A references a view file in Project B and Project B references a view file in Project A.
Local dependencies should go unilateral so we'll hit this error if we're referencing both ways.
The workaround is to make it one way - so if Project A is referencing view files from Project B, make copies of the view files from Project A in Project B.
This content is subject to limited support.