-
Notifications
You must be signed in to change notification settings - Fork 518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to complete browser login flow #134
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Yeah, I think this might be a limitation beyond our control. I've moved this out to #138 to track as a separate issue (this one is related to the Snap package). |
I experience same problem in Ubuntu: "Sign in" progress bar keeps running, but nothing happens. |
On Fedora 31 and FireFox you are able to do sign in in github but firefox doesn't return to application and instead displays an error page. |
I have the same problem using GitHub Desktop 2.0.4-linux1 / Ubuntu 18.04 LTS After validating the user, when callback, i get a 404 error instead of finishing the process in the application. I'm not able to sign in with the enterprise account. Tested with firefox and Chrome. 2020-04-01T21:06:20.148Z - info: [ui] proxy url not resolved, protocol not supported |
Hi, I use gentoo and downloaded the latest AppImage, happend the same over firefox, |
Closing this out as I don't have plans to revive Snap support |
Description
The latest
beta
snap can launch the browser login flow, but it doesn't seem to have the associated protocol handler registered to launch when the callback fires.Version
1.6.5-linux6
Steps to Reproduce
snap install github-desktop --beta --classic
Expected Behavior
Welcome wizard proceeds to next step
Actual Behavior
Nothing
Additional Information
I gather something needs to be declared in the
snap.yaml
file like this, based on the VSCode config:The text was updated successfully, but these errors were encountered: