How to Pack the Project with custom libraires using UiPath CLI in Azure Devops.
Issue Description
Unable to Pack the project with custom libraries using UiPath CLI in Azure DevOps.
Root Cause
This could be due to incorrect Service Connection details causing failure in authentication and consequently, inability to retrieve custom libraries. One potential reason is the presence of an Identity URL in the Service Connection, which is necessary only for PaaS environments, but not for Automation Cloud environments. If this Identity URL is provided for an Automation Cloud environment, it could lead to authentication failures in the orchestrator, thus blocking the retrieval of custom libraries.
Resolution
- Don't provide an Identity URL in Service Connection for Automation cloud environments.
- Make sure to provide the correct details in the Service Connection based on the UiPath environment and Authentication method.
Find additional information in this document.