Posting here because it does not seem to be documented anywhere else, or at least the search doesn’t return any results for this fix.
If you are getting LibGit2Sharp auth errors in Studio when attempting to perform git operations (clone, push, etc) to GitHub or GitHub Enterprise, all you have to do is create a system environment variable!
Name: UiPath_STUDIO_GIT_USE_SCHANNEL
Value: 1
Then just reopen Studio.
Hello @justin.cook!
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
-
Always search first. It is the best way to quickly find your answer. Check out the
icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution. -
Topic that contains most common solutions with example project files can be found here.
-
Read our official documentation where you can find a lot of information and instructions about each of our products:
-
Watch the videos on our official YouTube channel for more visual tutorials.
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
Cheers from your friendly
Forum_Staff
This worked perfectly for me. Just remember to create the system environment variable so that it is persistent. When I first tried it, I made the mistake of scoping it incorrectly.
Doesn’t seem to work for me. This happened when Git 2 factor authentication was activated and also right after upgrading to the new version of UiPath. Seems am stuck …
Did you ever get a fix? Are you using Personal tokens?
I seem to have found a solution. Looks like the credentails of git (amongst other things) are stored in the windows credential manager. If an old entry is being referred by git, which still has the old password or token, the push to git will fail. Check the relevant git entry in credential manager and update it with new password or token, then the push should work … see the image if it helps …