-
Notifications
You must be signed in to change notification settings - Fork 652
Troubleshooting
This document provides the information needed to troubleshoot common errors of LeetCode for VS Code extension.
The LeetCode Explorer is located in the customized activity bar, which is supported in VS Code 1.31.1+.
This means the extension is failed to start up. Mostly this is because the requirement is not satisfied. For example, the installed Node.js
version is lower than 8
.
There are multiple factors causing the user not able to sign in the extension:
-
You may use the wrong endpoint. Please Try to switch to the correct endpoint that you want to use.
Note: The accounts of different LeetCode endpoints are not shared.
-
If you are behind the proxy, please update the VS Code setting:
http.proxy
.You can trigger the command
Preferences: Open User Settings
to open the setting page.
Users cannot submit code until they have the email or phone verified in LeetCode.
The extension will hide the locked problems by default. You can enable the setting leetcode.showLocked
to see them.