Live-share: "Join session" link fails with "The owner of the workspace seems to be offline" when crossing multiple-regions

[KSLHacks]

Product and Version: VSCode 1.21.1
OS Version: macOS High Sierra v10.13.1
Live Share Extension Version: 0.2.260
Target Platform or Language: Does not apply

'Join session link' does not work as expected when using macOS.

• ❌Sharing from macOS: Windows users see "The owner of the workspace seems to be offline."
• ❌Sharing from Windows: macOS users see "The owner of the workspace seems to be offline."
• ✅Sharing from Windows: Windows users connect successfully
• _Note: do not have two macOS machines to test_

Steps to Reproduce / Scenario:

1. Start Live Share session on Windows 10 (VS Code 1.21.1 / Live Share 0.2.260)
2. Share link
3. Open link through macOS: "The owner of the workspace seems to be offline."
4. Open link through alternate Windows machine: Joins successfully

Note: When joining the session directly through VS Code Live Share Extension, it joins successfully (regardless of OS)

1. Open VS Code (either in macOS or Windows)
2. Select name > "Join Collaboration Session" > paste link
3. Joins session successfully

[Chuxel]

@KSLHacks Thanks for reporting this. We are having problems with cross-region joins. If one person is hitting east US and another is hitting west US (or Asia Pacific or Europe), the other person will appear to be offline.

However as a workaround you can manual join.

Can you confirm the region you are each hitting by running:
nslookup insiders.liveshare.vsengsaas.visualstudio.com

[KSLHacks]

Hey @Chuxel thanks for the fast response! We've been using this extension pretty extensively over the past few weeks and love it. Today was the first time having issues.

nslookup insiders.liveshare.vsengsaas.visualstudio.com
;; Got recursion not available from 157.56.74.180, trying next server
Server:     65.54.238.85
Address:    65.54.238.85#53

Non-authoritative answer:
insiders.liveshare.vsengsaas.visualstudio.com   canonical name = vsls-prod-ins-tm.trafficmanager.net.
vsls-prod-ins-tm.trafficmanager.net canonical name = vsls-prod-ins-usw2-180328000913.westus2.cloudapp.azure.com.
Name:   vsls-prod-ins-usw2-180328000913.westus2.cloudapp.azure.com
Address: 52.233.71.89

[KSLHacks]

As you pointed out, my colleague is hitting eastus.

[Chuxel]

@KSLHacks Thanks for confirming. We're working through this right now so stay tuned!!

[jkeech]

@KSLHacks, this should be fixed now. Let us know if you are still seeing this issue.

[KSLHacks]

@jkeech Thanks for the update, "user online" issue is resolved.

However, when clicking the link, VS Code opens > Live Share extension logs me in > does not connect to the session.

[Chuxel]

@KSLHacks That is likely a separate issue. Can you provide a bit more detail and your logs? That way we can determine if it is an existing bug reported elsewhere or something new. You can run the "Live Share: Export Logs" command in VS Code to get the logs.

[KSLHacks]

Hey @Chuxel, let me know what more info would help.

Same specs/versions as original post
Steps to Reproduce / Scenario:

1. Windows created a session and shared link
2. macOS clicks link
3. VS Code opens
4. Live Share Extension logs me in, but stops
   _Note: Joining collaboration session manually through VS Code works_

ExportLogs_03302018.zip

[Chuxel]

@KSLHacks Interesting - this could be a new bug. Here's the launcher line of interest:

Write to cascade.json error: The folder “cascade.json” doesn’t exist

That's indicating we're unable to store invite URI and hand it off to VS Code. Let me check with some folks, but I suspect we should open a new bug.

[Chuxel]

@KSLHacks Are you running Visual Studio Code out of a folder other than /Applications? If so, moving VS Code into the applications folder should resolve the issue. I'll raise a bug on this so we track a fix.

[KSLHacks]

@Chuxel VS Code is running out of /Applications. I have not moved it out.