Hi Daniel, 

I reached out to our Product Team, I'll let you know what they say when I hear back from them :) 

---

Hi Daniel, 

The Product Team advised

Looks like a Google restriction. When signing in with Google, RC redirects to Google, using the system's local browser (IE on Windows System). They would then follow Google's login process and once done, Google would redirect back to us. That error message looks to be while they are still on the Google sign part and would not be RC.

Sorry we don't have more information! Hopefully someone on Community has found a workaround :) 

---

Thanks for the information. A potential way that RC could mitigate the issue is to use the default browser setting rather than go with IE/Edge.

---

this seems to be similar to the Mac connection issue.  when inspecting the application interaction and handoff in chrome, the error states "user cancelled", then attempts to redirect to the app anyway which displays an error "no internet connection detected.....".  It doesn't appear that the google authentication is being able to communicate with the ring meeting app, possibly due to a compatibility issue between browser settings, security parameters, or other.  What i find odd is that ring central meetings forces the application with no possible fallback.  Open an app to open a browser to handoff back to the app..  This behavior is the same if opened form the web; force open app, open new browser tab/window for login, then handoff to app.  is the application not able to communicate the login directly?  why is it dependent on a browser interaction?  why have 3rd party authentication when the app cant even communicate directly with the4 3rd party?  the responses to the issue from RC thus far seem to push the issue onto various outside factors;Google, browser settings, firewalls, etc...  but it seems that is lies directly in the coding and service worker issues when forcing the handover to the app.

---