Can't publish library

[theEmailRobot (Email Robot)]

Hello,
I’m trying to publish a library I’ve created to use across a couple of projects, but I’m only getting the error message when trying to publish to Orchestrator Shared Libraries Feed:

23.10.0-beta.14233+Branch.release-v23.10.0.Sha.ac7649967f9e6f52cbf2d0156de91bd14e15f5cf

Error: Publish of Library project to Orchestrator failed. Package cannot be published to the shared feed

This is my first time really using Orchestrator so not sure if I’m even doing it right but I can’t figure out what to do next or how to pinpoint the source of the problem.

[Parvathy (PS Parvathy)]

Hi @theEmailRobot

Check out this thread. It might help you.

Publish Library to Orchestrator failed

I just found THE SOLUTION HERE in previous posts… It worked! Thanks for all your input guys!

Regards,

[theEmailRobot (Email Robot)]

I’ll do that, thank you!

[Gokul001 (Gokul Balaji)]

Hi @theEmailRobot

Check out this thread

Publish Of Library Project To Orchestrator Failed - Package Cannot Be Published To The Shared Feed

How to proceed when publish of library project to Orchestrator failed and package cannot be published to the shared feed? Troubleshooting Steps: The below procedure can be performed and verified Check if the Robot/ Studio is connected to the Orchestrator and make sure the Robot is assigned to any environment in the OrchestratorCreate a new sample library and check if the same error is receivedCheck if permissions for libraries in Orchestrator are provided. Navigate to tenant -> Manage Access -> …

https://uipath.my.salesforce-sites.com/CaseView/articles/Knowledge/Publish-of-Library-project-to-Orchestrator-failed-Package-cannot-be-published-to-the-shared-feed#:~:text=How%20to%20proceed%20when%20publish,published%20to%20the%20shared%20feed%3F&text=If%20the%20issue%20still%20persists,Technical%20Support%20for%20further%20assistance.

Regards
Gokul

[Yoichi]

HI,

It may be role matter. Can you check the following topic?
(Automation publisher role may be required)

Important updates in Orchestrator roles and permissions

Hello, UiPath community! We’ve been collecting your feedback around setting up roles and permissions in Orchestrator, and are pleased to announce a few upcoming improvements in the initial setup experience, as well as some important changes to the Automation User role. When creating a new tenant, you will notice a better separation of group roles by default. The changes to the default seeding are as follows: Updated group: Automation Users will no longer be able to access the Orchestrator UI…

Regards,

[theEmailRobot (Email Robot)]

I found the problem and for me it was that I had libraries set to be published with a API key which was empty for me on orchestrator, I wanted Secure Deployment anyways and switching to it fixed my issue of not being able to publish!