After converting a project from Windows-Legacy to plain Windows, I have a couple of activities that are not supported in this kind of project.
In the dependency tree, the dependencies belonging to these activities are displayed in red, with an exclamation mark on it (I’m attaching screenshots).
If you right click on it and choose the “Repair Dependency” option, then a “Reinstalling packages” dialog appear, while Studio does some stuff. When it finishes, the dependency appears in blue, as if it was repaired, but the truth it isn’t, and next time you reopen the project it will appear in red again.
This is misleading and leads to confussion.
Did you check if that package has a Windows (64 bit) compatible version? The UiPath Team activities are basically community resources developed by UiPath staff but often get abandoned when staff leave (would be great if you made the code open source at that point UiPath so we could continue them).
Its quite possible and likely that this package is only available in Windows - Legacy (32 bit).
No @Jon_Smith ; I didn’t. It’s already clear to me that the activities these dependencies belong to are not compatible with Windows projects. Did you read my report? The bug is that UiPath is saying that they are resolved, but they aren’t. If they aren’t, and that can’t be done, UiPath 1) shouldn’t offer the chance to attempt so, and 2) UiPath shouldn’t show it at resolved, if it isn’t.
To resolve dependencies that are not supported after converting a project from Windows-Legacy to plain Windows in UiPath, try manually removing the unsupported dependencies, and then adding the appropriate replacements (if available) by searching and adding the desired activities using the “Manage Packages” feature. Make sure to use the versions of activities that are compatible with your project.
Yeah @sai_gupta ; that’s clear. Did you read my last message, also? I was further clarifying what the bug is, and why it should be fixed. I think it’s clear enough. Thanks!
Think there is a typo here and you meant Windows projects.
My misunderstanding if you already knew the compatibility issue was indeed the root cause and instead just wanted to report the false repair.
Understood, I would say this is an edge case though and only affects projects undergoing conversion that have an incompatible depedency attached so not too serious of an issue.
Thanks for pointing out my type, @Jon_Smith ; you are right, I mean “plain” Windows projects. I already edited my comment.
About the “seriousness” of the issue: well, I’m facing dozens of “nonserious” issues with UiPath that all in all cause a lot of disturbance and slow down productivity a lot. If you think this is “serious” for a paid software with expensive licenses… I have a different view of it.
Agreed, that should not be the behaviour in this case. If failed (after a repair), inform the user the same.
False positive messages/behaviour should to be treated as bugs.
Thank you for reporting this.
Fair point and I hope you don’t misunderstand me as suggesting this shouldn’t be fixed as it is paid software.
I guess my point is this is only an issue so long as you are migrating, which should be a one off thing, and since I am done migrating many months ago I guess I don’t feel the pain