UiPath.CLI.Windows 24.10.9050.17872 fails to package in azure devops pipeline

Feedback Automation Ops
1

UiPath.CLI.Windows 24.10.9050.17872 was released today, and my ci/cd pipelines that rely on the UiPath.CLI.Windows to package processes are broken.
I have a ticket in with support, but I wanted to put this out raise awareness and see if others are having the same experience.

2024-10-11T13:42:40.1828121Z Unhandled exception. Autofac.Core.DependencyResolutionException: An exception was thrown while activating UiPath.Studio.CodedWorkflow.Shared.Services.Jit.DesignTimeBuildGenerator → UiPath.Studio.CodedWorkflow.Shared.Services.DesignTimeCodeBuilderService → UiPath.Studio.CodedWorkflow.Shared.Services.FileSystemProviderService → UiPath.Studio.CodedWorkflow.Shared.Services.SyntaxTreeCache.
2024-10-11T13:42:40.1829680Z —> Autofac.Core.DependencyResolutionException: An exception was thrown while invoking the constructor ‘Void .ctor(System.IO.Abstractions.IFileSystem, UiPath.Studio.CodedWorkflow.Shared.Interfaces.ICodedWorkflowFileService)’ on type ‘SyntaxTreeCache’.
2024-10-11T13:42:40.1830876Z —> System.IO.FileNotFoundException: Could not load file or assembly ‘System.Runtime.Caching, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’. The system cannot find the file specified.
2024-10-11T13:42:40.1832019Z File name: ‘System.Runtime.Caching, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’
2024-10-11T13:42:40.1833106Z at UiPath.Studio.CodedWorkflow.Shared.Services.SyntaxTreeCache…ctor(IFileSystem fileSystem, ICodedWorkflowFileService codedWorkflowFileService)

2

Hi @Peter_Lawson ,

Thank you for the quick feedback!
I will pass this on to the engineering team right away.

Alex

3

Hello @Peter_Lawson

Could you share with us your automation project in a PM so we can further investigate?

4

Aside this stack trace did the CLI output any .nupkg?

5

No .nupkg was created.

6

I’m happy for whatever help you can offer. Is it possible for us to work on this via the open support ticket that I have about this issue? #02484446

7

Just to update the status on this thread, the issue is solved and there was no bug in the newly released CLI. This was more of a configuration issue that didn’t surface in the older CLIs.

Important! I want to emphasize on the fact that running the CLI should be done with all the contents of the .nupkg that it’s packed in, missing any of the dependencies may cause errors and unexpected behavior.

@Peter_Lawson you may close the thread if the issue is solved.
Thank you for the early adoption of the new version and eager feedback!

8

Much thanks and appreciation to everyone on the UiPath support team for figuring this out for me. I’m a bit embarrassed to find that this error had been lurking in my pipeline for a long time, but so grateful to have UiPath as a highly capable and responsive partner!

1 Like
9

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