Just to shed some light on the problem at hand. If you are in one of the following scenarios, you will end up with a dependency cycle:
- you name your project “UiPath” (or any name of an existing package that you plan to add to your dependency tree)
- you open a .xaml file from a folder named “UiPath” (or any name of an existing package that you plan to add to your dependency tree) and there is no project.json file in that folder
In the first example with “UiPath” the problem is that there is already a package called “UiPath” that is a dependency for “UiPath.UIAutomation. Activities”. So the cycle will be UiPath > UIAutomation > UiPath.
In the second example, when you start a .xaml file from a folder and no project.json exists in that folder, a project.json will be automatically generated. Inside the project.json the tag “name” will be populated with the name of the parent folder. Which in this case is “UiPath”. So the same cycle happens as above.
Note that the UIAutomation package is added by default when you create a new project.
This is a corner case but at the same time this is a bug in our product and we will treat it in the following updates. Thank you.