Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

unable to complete browser login flow

See original GitHub issue

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

GitHub Desktop: 1.6.5-linux6
Operating system: Ubuntu 18.04

Steps to Reproduce

snap install github-desktop --beta --classic
launch the app
“Sign in using your browser”
Browser launches
Complete flow, browser indicates it is returning you to the app

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:

  url-handler:
    command: electron-launch $SNAP/usr/share/@@NAME@@/bin/@@NAME@@ --open-url
    desktop: usr/share/applications/@@NAME@@-url-handler.desktop
    environment:
      DISABLE_WAYLAND: 1
      GSETTINGS_SCHEMA_DIR: $SNAP/usr/share/glib-2.0/schemas

Issue Analytics

State:
Created 4 years ago
Comments:9 (2 by maintainers)

Top GitHub Comments

1reaction

pferiolicommented, Apr 2, 2020

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 2020-04-01T21:06:23.141Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 2.938s) 2020-04-01T21:32:47.123Z - info: [ui] [SignInStore] initializing OAuth flow 2020-04-01T21:32:47.138Z - info: [main] opening in browser: https://github.xxxxxx.com/login/oauth/authorize?client_id=3a723b10ac5575cc5bb9&scope=repo user&state=4a63ab04-f31d-494c-bbdc-2e2200e1a7ac

error

1reaction

shiftkeycommented, Apr 7, 2019

Note: On Chrome OS, the Linux world and the Chrome OS world are somewhat separate - I don’t know whether it’s possible for Linux apps to register protocol handlers that work in the main Chrome browser (though note that I know almost nothing about this setup, I just enabled it on a Pixelbook and decided to see what worked and what doesn’t).

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).