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.
After switching to the vscode-js-debug preview, Google warns that "This browser or app may not be secure."
See original GitHub issueDescribe the bug Upon clearing all browser data in my Chrome debugger instance, Google began complaining with a “Couldn’t sign you in. This browser or app may not be secure” error as seen here: https://pbs.twimg.com/media/EsqvRa8XMAE4OCv?format=png&name=small
This error appeared any time I attempted to login to ANY Google service within the launched Chrome instance.
Once I turned off the new built-in preview debugger and reverted to the long-used Chrome debugger, the Google warnings went away and was able to sign in again. My launch.json Chrome entry uses a separate profile:
{ "type": "chrome", "request": "launch", "name": "Launch Chrome against localhost", "url": "http://localhost:3333", "webRoot": "${workspaceFolder}", "userDataDir": "${workspaceFolder}/out/chrome", "skipFiles": [ "${workspaceFolder}/node_modules/**/*.js", "<node_internals>/**/*.js" ], },
To Reproduce Steps to reproduce the behavior: 0. Ensure built-in debugger preview is disabled
- Set up a separate Chrome profile using the old Chrome debugger VS Code plugin
- Ensure you are signed in to Google
- Enable the debugger preview in VS Code
- Launch debugger with preview debugger plugin
- Clear all browser data and ensure Chrome has no ties to Google account
- Close and re-launch debugger
- Attempt to sign into a Google service
- Google warns that they “Couldn’t sign you in” because “This browser or app may not be secure.”
VS Code Version: 1.51.1
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
After some experimentation, it seems this is caused by using
--remote-debugging-pipein the new debugger. Ironically this is more secure than the previous--remote-debugging-port, but causes the ‘security’ check on google login to fail. Not sure how they’re detecting that, since that should be invisible unless they have some special backdoor for google to detect debugging…You can have the debugger use the old port style by adding
"port": 12345(any open port) to your launch config. Let me know if that works for you.Documentation: https://code.visualstudio.com/docs/editor/debugging#_automatically-open-a-uri-when-debugging-a-server-program