Cannot connect to packages feed the deployment settings may be invalid

Hi, I had the same problem and I cleared that. I deleted some unused files file from the project. i.e custom output log files.

Hi Guys I solved this problem like that : When I wanna publish my project in studio I chose “Custom” and picked up any Folder to send it this folder.
This is the second step : Open your orchestrator platform and pick up the
Processes->Packages->Clik Upload->Browse and pick up file your published before as nupkg
It will probably be published.

I do as u said and still got that error :frowning: Any idea?

If you have documents in your project folder so delete all of them and then go project.json file and find “projectVersion” and make it “projectVersion”: “1.0.0” then publish it so it will be published.
Have a nice day.

I was experiencing the same error, I resolved mine because I had a file without an extension in the folder I was trying to publish, once I rectified this, I was able to publish.

Hi All,

I was facing same issue. Below are steps I perform and it resolves issue.

  1. Remove all files which are not used in your automation or generated through automation from your project folder.

  2. Publish project again.

Hope this will resolve your problem :slight_smile:

Omkar

1 Like

Hi everyone,

I am still receiving this error after deleting previous package files (and checking the file size of the new package to make sure it is not too big). I am set as admin for my machine as well.

I have also tried deleting all packages, the process, and the bot from Orchestrator in order to start completely fresh.

I am still receiving the error when I try to publish both with options “orchestrator” and “custom” in the Publish window.

I have looked into the settings in Studio, but I’m not really sure what I can edit to resolve this problem.

Any ideas?

Thank you in advance!
Shelby

Hello guys, i don’t know if you find a solution but for me the problem was that the new version that I want to publish it was having the same version like the version already published in Orchestrator. So in my case in project.json the version it was: “projectVersion”: “1.0.2” and in the Orchestrator it was the same version 1.0.2, already published.
I change the version in project.json and I was able to publish the process without problems or errors. :slight_smile:
I Hope this Help!

1 Like