"Not Found" on signing in
Description
When I sign in from dialog, error message "Not Found" appears. Username and password is correct.
What's wrong?
using package: github-for-unity-1.4.0.6503.unitypackage
Unity version: Unity 2019.4.12f1

By any chance, do you have 2 step verification on? In my case I had to click on "Sign in through web".
i had the same error
I have the same error.
Same here
Same problem here. The "Sign in through web" button was there at first, but now it is not...
Me too. "Sign in with your browser" doesn't work either.
Same Issue. What is the latest build of Unity this plugin actually works with?
Same here
Yer! I think the problem still persist. Same here.
same problem
Exact same problem.
Same problem.
Edit, however, the 'Sign in through web' button was available and did work. Hard to see though!

I also have this issue. Sign in with your browser shows just a blank page.
I also have this issue. Sign in with your browser shows just a blank page.
same issue
I also have this issue. Sign in with your browser shows just a blank page.
Yes, just show a blank page here as well. When I view the source of that page, it's really blank, HTML-less.
Since Unity has not addressed this issue there are two possible solutions, use git from the command line or use the git hub addon in Visual Studio Code. Both will allow you to do exactly the same thing. This is a band-aid for a feature that doesn't work properly.
Same here
Same here
same. cant log in with username or with "sign in with browser"
I either get "not found" or "invalid token". Also, the browser tab that opens doesn't display anything, only a localhost URL and a blank page
Same problem. localhost URL is a blank page too. On the first attempt, the page showed up. Then it failed everytime
same. cant log in with username or with "sign in with browser"
I either get "not found" or "invalid token". Also, the browser tab that opens doesn't display anything, only a localhost URL and a blank page
Exact same problem here (and had it for a few weeks now).
Visual Studio and VS Code both still work, so for everyone still stuck with this: Try using the VS GitHUB extension to push/pull. You can still commit to the local stash in Unity (at least this still works for me) and then execute a sync in VS. Both views should sync up after the transaction.
Same here
Same here. Sucks. This would really be nice.
Edit: On using the browser link, after being confronted with the blank HTML page and going back to unity, I get an error: "Error Validating Token".
Also, the page is not calling out to github; it's pointing to a local URI: http://localhost:42424/callback?code=c8ca6573bb08d91389ab&state=f3bd1061-9bc3-4ebc-acdf-7dd42def50d7
I'm guessing this is the issue?
I'm getting this exact problem too. Only gives me the web link to sign in. Seemed to send me to the github page once, but I got the "error validating toke" error and it always sends me to http://localhost after that.
Finding bug reports very similar to this that go back for years.
Having the same issue. I'm on Unity 2019.4.16f1. Two factor authentication is not enabled. Using GitHub for Unity version 1.4.0.
I have the same problem. But I actually don't need to be autorized to use this plugin. My way:
- Create the repo on github
- Initialize the git in your project
- Copy the git path into "origin"
- Be sure that, your ssh applyed in your github settings
- Commit and push as well.
I'm having this issue as well.
So this issue has been happening for over a year, and no word from Unity on when/if it will be fixed?
no word from Unity
I think maybe this is more github's responsibility.
i have the same problem, logging in through unity: "Not found", trying with the browser results in a blank page as well.
no word from Unity
I think maybe this is more github's responsibility.
Well, in 2020 GitHub announced their intent to update their authentication process to require token-based authentication on all platforms. This new measure was implemented and is required since around August 2021. It's was up to Unity to develop a solution that supports the new authorization flow. But alas, it's been almost 2 years and as you can see they still haven't done so.