Live-share: Logging into Microsoft or Github stalls

Created on 11 Oct 2019  Â·  22Comments  Â·  Source: MicrosoftDocs/live-share

I always get this stalling notification whether or not I'm using a firewall or a GitHub/Microsoft account.
I am still able to connect to live shares from other users with my firewall disabled.

Live Share Logs.zip

Product and Version [VS/VSCode]: Code 1.39.1 (88f15d17dca836346e787762685a40bb5cce75a8, 2019-10-10T23:35:11.314Z)
OS Version [macOS/Windows]: macOS 10.15
Live Share Extension Version: 1.0.950
Target Platform or Language [e.g. Node.js]: N/A

Steps to Reproduce / Scenario:

  1. Click Live Share in status bar
  2. Click either the Microsoft or GitHub sign in button
  3. Sign in
  4. See success page in browser
  5. See stalled message in VSCode (screenshot below)

Screenshots
image

identity and sign-in logs attached startup

Most helpful comment

It still does not work for me even if I'm already signed in.

All 22 comments

I have the same issue, but I can neither start nor join a Live Share session. The stalled message says Sign In to Proceed for me. I have tried uninstalling and reinstalling the extension, closing and reopening VS Code, but none of those options work.

I’m still able to join another’s session as a guest, can you?

I can join as a read-only guest without any issues.

Hi, thank you for reaching out and attaching your logs. is your browser is Google Chrome ? We have a fix for chrome sign in issue which will be released soon.

adding @Moniarchy for info

Yes, latest stable release of Chrome

I have this issue but I happen to use Safari. Have tested this with Firefox and I get the same results.

@nickmccurdy @rzhong9963 are you eventually able to sign in? Are you always initiating the authentication process from VS Code as opposed to starting from the browser and using the user code to log in?

@rzhong9963 could you also attach your logs if you see this problem again?

No, I’m not able to sign in to start any sessions, I can only join other sessions as a guest.

I was not able to sign in at all and I always initiate the authentication process from VS Code.
I have attached the log files. I only have the logs files for when I tried it again today as I did not enable logging before.
Logs.zip

When I initiate a new LiveShare instance after being directed to sign in, and I do, and get a confirmation of authentication, LiveShare says signing in but never does. I am only able to accept an invitaion in read-me mode. I'm using os 10.15.xx - Catalina, if that matters.

Extension version: 1.0.950
VS Code version: Code 1.39.1 (88f15d17dca836346e787762685a40bb5cce75a8, 2019-10-10T23:35:11.314Z)
OS version: Darwin x64 19.0.0

CPUs | Intel(R) Core(TM) i5-4250U CPU @ 1.30GHz (4 x 1300)
-- | --
GPU Status | 2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled
Load (avg) | 5, 5, 4
Memory (System) | 4.00GB (0.08GB free)
Process Argv | -psn_0_2777766
Screen Reader | no
VM | 0%

I've been having the same issue since upgrading to Catalina (10.15)

Attempting to create a new Live Share (or just attempting to login to Live Share) I can go through the auth process as normal, but once closing the tab in Chrome VSCode doesn't acknowledge any change and I see the same hanging message as screen-shotted by OP.

I'm still investigating this. @nickmccurdy, @rzhong9963, @Alendor22, is this still affecting you? What happens if you try signing in before trying to start a session, as opposed to starting a session while being signed out and continuing the authentication flow from there?

If you try this and this works for you, can you share your logs again so I can compare them?

It still does not work for me even if I'm already signed in.

Does Live Share try to sign you in if you are already signed in or are you seeing different behavior?

It still tries to sign me in every time I want to start a session.

I still can not log in, I am already logged into github as well, LiveShare just needs to be authenticated via github.

Sent from my iPhone

On Oct 23, 2019, at 6:19 PM, Robert Zhong notifications@github.com wrote:


It still tries to sign me in every time I want to start a session.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hello,
It seems to be broken since catalina update too. I try to login using code with no luck since the proccess stalled too.

This sounds very similar to #2926
I've described my experiences there: https://github.com/MicrosoftDocs/live-share/issues/2926#issuecomment-549510050

I can log in using the instructions found here
https://github.com/MicrosoftDocs/live-share/issues/2926#issuecomment-549593019

Fixed for me, but I'll reopen if someone can confirm it's still an issue

Was this page helpful?
0 / 5 - 0 ratings