-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSCode still requiring an API key although one is set inside .wakatime.cfg
#256
Comments
It should... the vscode plugin doesn't have any other way to get your api key. Maybe your |
Sometimes it pops up for no reason and I have to re-enter the API Key. |
That’s the behavior I do encounter as well. I double checked it the files. I’ve first created the config file. I then installed the extension. And upon first launching vscode with the extension, it prompted me for the key. Even though the key was present in the confit file. |
Please send your You might need to turn on debug mode for the error message to be logged. Edit: Also, the next time it asks for your api key before entering it can you send the contents of ~/.wakatime.cfg to support@wakatime.com? Maybe the cfg file is getting corrupted somehow. |
|
Do you also use Atom with WakaTime? We just fixed a bug in the atom-wakatime plugin that might have been corrupting your |
I am having this issue as well, it is very annoying. If you try to ignore it, it will pop up every time a file is saved, opened, or closed. It forces you to add the key to stop being bothered by it. Sometimes it will last for a few days without asking again, other times it will ask after a couple of hours |
@jeetsdev what's the contents of your |
Here it is-
|
That's valid and shouldn't cause the |
Yesterday I was encountering the same bug as @mrgnhnt96. I input my key multiple times, disable and enabled wakatime extension (from the command palette) and nothing worked. The extension kept asking me for the api key. Today it's working again with no additional changes on my side 🤷♂️ |
Can you try with the latest release just now v18.0.5? If it's still asking for your api key after updating the plugin, please add a comment here with your:
|
@alanhamlett over the past 5 days it seems to bo working correctly. Not once I was asked for the api token and everything is tracked properly. |
I'd expect the extension to pick the key from the configuration file automatically without me having to enter it in again.
The text was updated successfully, but these errors were encountered: