unable to complete authentication flow from browser

[RicardoGavilanez]

Describe the bug

Write a clear and concise description of what the bug is.

Version & OS

Version: 2.9.9 Linux RC 2
OS: Ubuntu

Open the 'About GitHub Desktop' menu to see the GitHub Desktop version. Also include what operating system you are using.

Steps to reproduce the behavior

1. Go to 'Sing in to github.com'
2. Click on 'it'
3. login in GitHub
4. not login in the GitHub Desktop

Expected behavior

It should sign in to GitHub Desktop and allow me to look at and work with my projects.

Actual behavior

It does not allow to log in, in linux it only stays loading and even if you log in in the browser it does not log in to the program.

Screenshots

Logs

Attach your logs by opening the Help menu and selecting Show Logs..., if applicable.

Additional context

Add any other context about the problem here.

[shiftkey]

Please locate the log files directory from the Help | Show logs in your File Manager menu item and include a recent log from when this problem was occurring.

Without more information about the underlying error I suspect this is a generic issue with the app not being able to store the token from the OAuth signin flow on your local machine...

[willianholtz]

yeah, I can't login either. On fresh installation of my arch Linux:

The same asks to log in via browser, when coming back it looks like this on this screen!

[shiftkey]

@willianholtz there's extra details which are important here that would help me to confirm whether you have this same issue or whether you have something like #677 (comment) - please check the log files using the note in my previous comment

[willianholtz]

it's the same problem. However, and I went back to version 1.9.4 I logged in and updated to the newest version, it worked again. But before that, I made a backup of the github folder in .conf, and after all the procedures, I returned the backup to the folder.

[shiftkey]

it's the same problem.

This is the bit I'm not sure about - the original comment doesn't include any logs - just a screenshot. Could you share some logs from when you were seeing the login flow fail?

[thyeun]

@shiftkey still not possible to login using latest version 2.9.12 with arch linux distro

Below are the log file

2022-04-03T17:59:12.308Z - info: [main] Received possible protocol arguments: 4
2022-04-03T17:59:12.309Z - info: [main] Processing protocol url
2022-04-03T17:59:12.312Z - warn: [ui] Unknown URL action: unknown - payload: {"name":"unknown","url":"--enable-crashpad"}
2022-04-03T18:03:39.207Z - info: [ui] [AppStore] loading 0 repositories from store
2022-04-03T18:03:40.800Z - info: [ui] launching: 2.9.12-linux1 (Linux 5.17.1-arch1-1)
2022-04-03T18:03:40.804Z - info: [ui] execPath: '/opt/github-desktop/github-desktop'
2022-04-03T18:04:09.431Z - info: [ui] [SignInStore] initializing OAuth flow
2022-04-03T18:04:09.437Z - info: [main] opening in browser: https://github.com/login/oauth/authorize?client_id=3a723b10ac5575cc5bb9&scope=repo%20user%20workflow&state=24df6324-a2b2-4576-9c31-9833372ff868
2022-04-03T18:04:15.403Z - info: [main] Received possible protocol arguments: 4
2022-04-03T18:04:15.408Z - info: [main] Processing protocol url
2022-04-03T18:04:15.412Z - warn: [ui] Unknown URL action: unknown - payload: {"name":"unknown","url":"--enable-crashpad"}
2022-04-03T18:04:55.179Z - info: [ui] [SignInStore] initializing OAuth flow
2022-04-03T18:04:55.220Z - info: [main] opening in browser: https://github.com/login/oauth/authorize?client_id=3a723b10ac5575cc5bb9&scope=repo%20user%20workflow&state=28756892-9efd-4484-8e77-704adcc1e9fa
2022-04-03T18:04:58.739Z - info: [main] Received possible protocol arguments: 4
2022-04-03T18:04:58.741Z - info: [main] Processing protocol url
2022-04-03T18:04:58.751Z - warn: [ui] Unknown URL action: unknown - payload: {"name":"unknown","url":"--enable-crashpad"}

[shiftkey]

still not possible to login using latest version 2.9.12 with arch linux distro

@thyeun please note that 2.9.12-linux2 is the build with this fix - you are using 2.9.12-linux1 which does not contain the fix.

[thyeun]

@shiftkey Understand, but 2.9.12-linux2 still not possible to login

Below is the log file for 2.9.12-linux2

2022-04-03T18:15:18.285Z - info: [ui] [AppStore] loading 0 repositories from store
2022-04-03T18:15:18.705Z - info: [ui] launching: 2.9.12-linux2 (Linux 5.17.1-arch1-1)
2022-04-03T18:15:18.714Z - info: [ui] execPath: '/opt/github-desktop/github-desktop'
2022-04-03T18:15:30.980Z - info: [ui] [SignInStore] initializing OAuth flow
2022-04-03T18:15:31.058Z - info: [main] opening in browser: https://github.com/login/oauth/authorize?client_id=3a723b10ac5575cc5bb9&scope=repo%20user%20workflow&state=afe56fdb-555a-43c8-87b6-64c82c4c8f79
2022-04-03T18:15:34.703Z - info: [main] Received possible protocol arguments: 4
2022-04-03T18:15:34.705Z - info: [main] Processing protocol url
2022-04-03T18:15:34.707Z - warn: [ui] Unknown URL action: unknown - payload: {"name":"unknown","url":"/usr/bin/github-desktop"}

[shiftkey]

@thyeun ok, that's helpful. But this is a different issue to the topic at hand, which I'm dealing with multiple reports about:

• Unable to complete authentication doing browser flow - --enable-crashpad received #677 (comment)
• Can't log into github desktop #666 (comment)

Please follow along there for updates.

[thyeun]

@shiftkey is ok, just wait for the solution since i still can done things using web version. :)

[thyeun]

@shiftkey Any info you still need for #677 and #666 ?

[RicardoGavilanez]

EN LA VERSION [2.9.12 Linux RC4] SE ARREGLA EL PROBLEMA MUCHAS GRACIAS

[shiftkey]

Closing this out due to inactivity - the latest 2.9.12-linux4 release should fix this issue, based on what others have reported in other issues