Error Detecting project version - KB

News Knowledge Base
1

How to fix the error "Error detecting project version" thrown from UiPath Studio while opening the project or executing a process?

Cause: This error usually occurs when the project is being developed with higher version of UiPath Studio than the Robot version where it is being executed.

Resolution: Note that UiPath doesn’t support forward compatibility which means a project developed in the higher version will not run on the lower version.
Hence, either upgrade the Robot to same version as Studio or re-develop the workflow on development machine where you have same version of Studio as Robot version.

If the above solution does not seem feasible for some reason, the below work-around can be tried on the Robot machine but that might require some changes in the workflow as following:

  1. Make a note of the current dependencies in the project. This can be done from the "Manage packages" window or from the Project panel window. Please ensure to make a note of the activity dependency version number also.
  2. Take a backup and delete the project.json file found inside the project folder. (The project.json file also contains the record of the project dependencies that you would take a note of in Step 1, this can also be used as a reference)
  3. Re-launch the project using the UiPath Studio. This will re-build the project.json with the default versions of activity packages.
  4. Observe if there are some of the activities showing errors. This is because some activities have been changed in higher version. To fix this, check if the activity package version noted in Step 1 is compatible with Robot version. If yes then upgrade the package version and it should be possible to see the activity. If not then follow the below steps :

A. Open that xaml file in development environment
B. Locate the activity in question, note down the value of the activity's properties and delete it later
C. Save the xaml and copy to the Robot machine
D. Open the updated xaml file and add the activity again.

Note: Perform the same steps for all the activities throwing error because of non-compatibility.