Broken dependencies after opening project with new studio version

Help Studio
, ,
1

Hello everyone

I opened a legacy project in a new studio version (22.10…)

and i found all my dependencies to be broken

image

i have opened other similar products and it was not the case

I tried clicking “repair dependencies” but it still goes back to the same state

Thank you

2

Instead of Repairing the dependencies try to reinstall the dependencies.

3

Hi

If repairing doesn’t work then remove the package and try to reinstall by going to Manage Packages and install them under ALL PACKAGES

image

Cheers @adext

4

Looking at the long version number of the packages they are really, really old.
Not all of those older packages are compatible with the newer version of a studio.

And, if you also upgraded your orchestrator (in case of on premise installations) and the person doing the upgrade basically made a clean install instead of a migration, those older packages might not even exist on your server anymore.

Try to upgrade your dependencies at least to versions matching your studio. The activities themselves are 99% backwards compatible so going from 18.x to 22.x should most likely not cause issues.

5

Go into Manage Packages and add back in the old feed:

https://www.myget.org/F/workflow/

6

Hi @adext

When you open a legacy project in a new version of UiPath Studio, it’s not uncommon to encounter issues with broken or incompatible dependencies. Here are some steps you can take to address this problem:

  1. Update Dependencies:

    • Check if there are updates available for the packages and dependencies used in your project. You can do this by going to the “Manage Packages” window and selecting the “Updates” tab. Update any packages that have newer versions available and are compatible with the new Studio version.

  2. Check for Compatibility:

    • Ensure that the packages you’re using are compatible with the new Studio version. Sometimes, older packages may not work well with newer versions of Studio. If you’re using custom or third-party packages, make sure they are compatible.

  3. Review Project Settings:

    • Open the project settings (project.json file) and verify that the dependencies listed there match the packages installed in your project. If there are any discrepancies, update the project settings accordingly.

  4. Rebuild Dependencies:

    • Sometimes, clicking “Repair Dependencies” may not resolve all issues. Try the following steps:
      • Close UiPath Studio.
      • Delete the project.json file from your project folder.
      • Reopen UiPath Studio and open your project again. It should automatically recreate the project.json file and rebuild the dependencies.

  5. Recreate Your Project File:

    • As a last resort, you can create a new project in the new Studio version and manually copy your workflows and assets into the new project. This can be time-consuming but ensures that you start with a clean project structure.

  6. Check Logs and Error Messages:

    • Review the error messages and logs in UiPath Studio. They may provide more specific information about the broken dependencies.

  7. Support and Documentation:

    • If you’re still facing issues, consider reaching out to UiPath Support or consulting UiPath’s official documentation for guidance on upgrading legacy projects.

It’s essential to back up your project before making significant changes and to ensure that you have version control (if applicable) to track and revert changes if needed. Upgrading legacy projects to new Studio versions may require some effort, especially if there have been significant changes or updates to the packages and dependencies used.

Thanks!!

7

This is incomplete, and somewhat dangerous advice. Important settings can be lost by doing this. Also, it resets the dependencies back to the Studio default which can break activities due to being a downgrade in some cases. It will also reset a library back to a process. You should never delete project.json, but it’s ok to rename it for testing purposes. Project.json is rarely the cause of any issues.

8

This is already tried and tested solution and worked fine. There is nothing dangerous or incomplete. Please don’t misguide others.

9

I explained what’s dangerous and incomplete. Didn’t you ever notice it resets all your dependencies to the Studio default? If the problem is a network issue that makes it so you can’t download packages, this doesn’t solve it - it just loads the local default packages. I’m not the one misguiding people. Or take a library, delete project.json, open the project, and see what happens. It won’t be a library any more. There are many problems that can be caused by deleting project.json.

10

deleting project.json and reopening the project resolved the issue
thank you

1 Like
11

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.