Closed alanhamlett closed 2 years ago
Having substantially the same behavior (no error though)... I keep getting prompted for the API key, and it's got the correct key there prepopulated, where i can just hit enter.
I checked the settings file, and see that the key is correct there too.
So far no time getting recorded, though I've been on it ~10-12 hours past couple days.
I do keep getting this in the developer console: [WakaTime][WARN] Unable to get api key: Error: spawn EPERM
@aggietallboy are you on windows?
@aggietallboy thanks for the error message! That shows it's caused by vscode-wakatime not wakatime-cli. Can you update to v18.0.6 of the plugin, turn on debug mode, then share your vscode dev console logs when it happens again?
Hi, I also have this issue, on Windows 11, using v18.0.6, here are the dev console logs with debug mode on:
Also, Windows Security is flagging Wakatime all of the sudden, this might be related
Further, when you allow the wakatime-cli-windows-amd64.exe to run in Windows Security, it works again.
Closing as duplicate of wakatime/wakatime-cli#691. Let's move the conversation there.
@steventango the windows security issue is https://github.com/wakatime/wakatime-cli/issues/654
I’ll sure try!
I'm having the same problem, at least with VScode. The plugin reports "WakaTime Error" and asks for the API key, which is valid. I even reset it a few days ago to make sure. It recorded my time on the 20th and 23rd, but not the 21st, 22nd, 25th, or today, and I did at least a few hours each day. I'm able to connect to the website fine. It's just the VSCode plugin that's not working.
Originally posted by @Perlkonig in https://github.com/wakatime/vscode-wakatime/issues/247#issuecomment-1001202497