Hi, I’m using Community edition and after last Studio updates to 2023.4.0, I have noticed strange issue when publishing our custom company’s libraries to Orchestrator.
I have two versions of libraries published in Orchestrator: for Windows-Legacy projects and for Windows projects, now recently when I published those for Windows (with just few changes), I have noticed, that there was also created a strange library with “Library.Runtime” added in the name:
I’m not sure what is this and why it was automatically published along with my original Libraries?
The same is now available in Studio in Manage Packages:
When I deleted those with Runtime from Orchestrator, projects with already updated libs got broken, so I had to re-upload them again. Is it something new related with Windows projects or is it some kind of error maybe?
I have a little actualization after last Studio update to v2023.4.0 Beta - additional “.Library.Runtime” disappeared from Studio - Managa Packages window:
But they are still visible in Orchestrator - Packages - Libraries:
Looks like the latest release (community license version) has fixed the issue.
However, I’m facing a new issue previously mentioned here: Custom activity package not visible
→ I can’t see my custom activities from installed Nuget package in UiPath Studio. Unless I “created nuget package with name ending as “.activities””.
I don’t know what you mean by saying that they fixed it. But there are still two entries in the libraries in orchestrator, one with just the name and the other with .Library.Runtime appended to it. Just to test it out, I removed the reference to the one WITHOUT the runtime library and the bot code compiled just fine. I will post an update after running the bot with just the runtime.
Hi @Piotr_Gajewski ,
When You publish the custom libraries, Go to Project Settings there is on option like separate runtime dependencies and Disable it.
