This more or less the same problem we have, our pipelines deploy but we cannot even run it.
I have no idea how to debug this sudden issue and we had diverted several projects to use the new process type specifically because it was indicated that we needed to, instead we have a deprecation scary-gram on every window and every attempt at upgrading has broken something
We have the same issue. No clue of how to fix it.
Same here, process not working at run stage
I work with @Joshua_Rowlison and we have yet to resolve the issue. As Josh stated we have put a lot of work into getting everything flowing through the ADO Pipelines. Any updates or acknowledgement of the issue would be greatly appreciated.
We’re having the exact same issue. So far only option is to publish via studio. We’ve delayed our migration to windows compatibility until this is resolved.
Sorry, I am very junior in UiPath programming but, how can we proceed then? I have create a new xaml within an old library that was use in a projects in the Legacy scheme. I have done the same: modify the xaml in the library and try to publish it so that I could use this xaml as an activity in my Legacy projects that used it. However, when I try to publish it, the system is throwing tones of validation errors of all projects I have, and concluding that I cannot publish the library project because I have all these validation errors. Can anyone help to find a way to get my library with my new xaml accesible for my old projects in Legacy system? I am about to loose many months of work!!!
Curious if there are any updates here or an ETA on when this might be fixed?
I had this problem as well. The issue for me was that the Build Pipeline was using the wrong version of the cli tool.
All we needed to do was add the UiPath Install Platform task in the Pipeline before the UiPath Pack task.
Lastly, recreate the UiPath Pack task.
After that, you may get an error in the UiPath Pack task saying “##[error]Error packaging project: Error: Parameter ‘toolPath’ cannot be null or empty.”
The fix for this was that our projectJsonPath parameter for the UiPath Pack task was pointing to a folder that was one level above where the actual project.json file was. In previous Windows-Legacy project pipelines, this wasn’t an issue for us, but it seems that for this Windows CLI version, it needs to be the exact folder path.
I am facing the same issue and tried your advise to add UiPath install Platform but getting error like this:
installing platform: Error: end of central directory record signature not found.
Do you have any idea on my issue?
I have solved this problem by download UiPath.CLI.Windows.22.10.8438.32859.nupkg at https://uipath.visualstudio.com/Public.Feeds/_artifacts/feed/UiPath-Official
And put CLI.Windows.22.10.8438.32859.nupkg path at here:
So this is the step that I’ve done:
Hope this help
Hi everyone,
we have meanwhile published a new version of the plugin supporting the packaging of modern projects.
Pls let me know if this has solved your problem or if further assistance is required.
BR
Thomas
For us it works fine since the latest plugin update.
BR
What did you make your projectjsonpath? I used the install and am getting that error about the parameter ‘toolpath’. I tried many different possible paths but nothing seems to be working for me.
Hi,
Is the solution just to be using the latest version of the integration plugin? Would that be version 3.0.3517186?
projectJsonPath: ‘$(Build.SourcesDirectory)\src’
My project ‘project.json’ file is inside my ‘src’ folder of my Git repository.
If your project isn’t inside any folders in your git repository, then it would just be ‘’$(Build.SourcesDirectory)'.
Thats how I had the parameter previously so I dont need to change anything but I am still getting that error.
My src is just the name of my project and inisde that folder is my project.json.
I finally got back to trying to get this to working again. I’ve got the new version of the cli working but for when I use version 3 of the UiPath Pack it always fails to authenticate to our orchestrator to restore custom nugget libraries. When I switch it back to version 2 it doesn’t fail to authenticate but also doesn’t build the nugget package correctly for the windows package. Anyone else experiencing this?
This was also the missing part for me.
Thank you.
Yoichi
ppr
Anil_G
Parvathy
Niranjan_k
Mohan_Reddy
Vandekamp
lakshmi.mp
uio
rikulsilva