You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Mac Mini and a MacBook. On both of these, when I installed it the first time, it didn't sign in. I had to delete the extension and reinstall it to sign in. After using it for a day, it's not connecting anymore and isn't giving any error. I've attached the screen recording for reference.
Hi @Saqlain-ch, sorry to hear that you are dealing with this - could you ensure the logging level is set to trace in the Colab user settings and share the resulting Colab logs here? The additional information captured by the trace logs will help us to better troubleshoot the issue. Thanks!
Hi @mounikasomisetty, The version of the Cloab extension is the latest one as I've deleted and installed it multiple times. To be specific, it's 0.2.1, and VS Code 1.109.0, both are on their latest version.
Thank you for confirming that @Saqlain-ch - I'm not fully sure why this is happening but my guess would be that the authentication pop up is getting blocked, there is a network issue or a corrupted cache. We are still looking into it though.
Sorry your hitting an issue. From the logs, the two relevant pieces are:
Error: request to https://oauth2.googleapis.com/token failed
Error: Timed out waiting for authentication provider 'google' to register.
The google authentication provider will only fail if the extension fails to activate. Activation failures will appear in Output > Extension Host (or Output > Extension Host (Remote), if connected to a remote VS Code server). Can you pass those along?
@kevineger Sure! When I try to select a new Colab server, it triggers these lines in Output > Extension Host
Let me know if I can provide any other diagnostics or try something.
2026-03-03 17:38:03.444 [error] Error: Timed out waiting for authentication provider 'google' to register.
at lYe.G (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607:73789)
at async lYe.getSessions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607:70806)
at async zui.I (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607:79065)
at async zui.$getSession (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607:80930) jupyter.kernel.selectJupyterServerKernel {"value":"ms-toolsai.jupyter","_lower":"ms-toolsai.jupyter"}
2026-03-03 17:38:03.444 [error] Error: Timed out waiting for authentication provider 'google' to register.
at lYe.G (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607:73789)
at async lYe.getSessions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607:70806)
at async zui.I (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607:79065)
at async zui.$getSession (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607:80930) jupyter.kernel.selectJupyterServerKernel undefined
Activity
mounikasomisetty commentedon Feb 9, 2026
Hi @Saqlain-ch, sorry to hear that you are dealing with this - could you ensure the logging level is set to trace in the Colab user settings and share the resulting Colab logs here? The additional information captured by the trace logs will help us to better troubleshoot the issue. Thanks!
Saqlain-ch commentedon Feb 9, 2026
Hi @mounikasomisetty, I've atteched screenshot and text of the output.
Saqlain-ch commentedon Feb 9, 2026
Hi @mounikasomisetty, I've changes logining access to trace and now this is the output logs
mounikasomisetty commentedon Feb 10, 2026
Thank you for providing that @Saqlain-ch ! Could you also confirm what version of the Colab extension you are using?
Saqlain-ch commentedon Feb 10, 2026
Hi @mounikasomisetty, The version of the Cloab extension is the latest one as I've deleted and installed it multiple times. To be specific, it's 0.2.1, and VS Code 1.109.0, both are on their latest version.
mounikasomisetty commentedon Feb 11, 2026
Thank you for confirming that @Saqlain-ch - I'm not fully sure why this is happening but my guess would be that the authentication pop up is getting blocked, there is a network issue or a corrupted cache. We are still looking into it though.
kevineger commentedon Feb 23, 2026
Sorry your hitting an issue. From the logs, the two relevant pieces are:
Error: request to https://oauth2.googleapis.com/token failedError: Timed out waiting for authentication provider 'google' to register.The google authentication provider will only fail if the extension fails to activate. Activation failures will appear in
Output>Extension Host(orOutput>Extension Host (Remote), if connected to a remote VS Code server). Can you pass those along?[-]Can't not connect to server[/-][+]Extension activation failure.[/+]lasse-meixner commentedon Mar 4, 2026
I have exactly the same issue.
kevineger commentedon Mar 4, 2026
As above, mind passing along your
Extension Hostlogs @lasse-meixner?lasse-meixner commentedon Mar 4, 2026
@kevineger Sure! When I try to select a new Colab server, it triggers these lines in
Output > Extension HostLet me know if I can provide any other diagnostics or try something.