Facing an issue with managing packages

[Vaisakhnath_C_K]

Hello,

I am a beginner in UiPath automation and recently started exploring browser UI automations. I have installed UiPath Studio v10.22 on my Virtual Machine and began working on some projects. However, when I try to open a project, I encounter an error related to package dependencies. I have already tried reinstalling UiPath and upgrading the packages through the “Manage Packages” section, but the issue still persists.

I have attached screenshots of the error for reference. Any help or suggestions to resolve this would be greatly appreciated. Thank you!

[Kismet_Tosun (Kısmet Tosun)]

Hi @Vaisakhnath_C_K

The project is made in a different version. Check the current version or right click on the dependencies shown below and update

[Venkat4 (Srikanth BV)]

Hi @Vaisakhnath_C_K

This error is appearing since you are opening a process which is developed in windows legacy mode. Please click on “Covert to Windows” link on the top and it will convert your process to windows compatible package and it repairs the packages as well.

Also you need to make sure the third party packages are supported by the windows compatible processes and if not you need to replace those packages with the compatible ones.

Hope this helps.

Cheers

[ashokkarale]

@Vaisakhnath_C_K,

First 3 packages are custom packages developed by your organization so you should have the nuget package of these packages to install in your project.

For remaining packages, you should be able to install the package from official feed.

I would advise to no to upgrade the project from Legacy to Windows before you check the compatibility of the first 3 packages with Windows compatibility.

If you convert the project to Windows and your packages are on Legacy, your project won’t work.

Thanks,
Ashok

[Anil_G (Anil Gorthi)]

@Vaisakhnath_C_K

Welcome to the community

if you create a new project also are you getting some error? if so the feeds are not accessible check the same

if not then that means your studio is on a lower version than the packages version also your orchestrator if it is lower version and on prem then might not have the latest versions which again is a very less chance

you can right click and click repair packages always

for the custom packages you need to make sure you upload them to orchestrator feed or add a local feed which contains those .nupkg files

cheers