search

wakatime / vscode-wakatime

Visual Studio Code plugin for automatic time tracking and metrics generated from your programming activity.
https://wakatime.com/vs-code
BSD 3-Clause "New" or "Revised" License
1.24k stars 137 forks source link

VSCode always asks for API key - another warning #336

Closed ACnoway closed 1 year ago

ACnoway commented 1 year ago

just like #324 , vscode started to ask me API key even after I regenerated new key and put in for like ten times. vscode version: 1.77.3 wakatime extension version: 24.0.9 the warnings in developer tools looks like this: wakatime bug and I didn't see anything in .wakatime.log

J-Ciro commented 1 year ago

Same here, nothing related to Denfender.

YatsukiRenka commented 1 year ago

Same trouble, yesterday it was fine but happened this morning

nekochan0122 commented 1 year ago

Same here, it happened after I update the extension.

zhangkaihua88 commented 1 year ago

Same here

FE-wuhao commented 1 year ago

it start to happened from this morning

staff0rd commented 1 year ago

I've seen this occur before and eventually go away, however the frequency of the popup (pictured below) is extremely frustrating considering ESC or the correct API key doesn't resolve the issue.

It would be pleasant if there were some kind of exponential backoff on displaying the popup, regardless of whatever the actual fix for the underlying error.

image

For now it causes me to disable the extension and (hope to) remember to enable it later.

DavoDC commented 1 year ago

I'm getting it too. I downgraded to 24.0.7 and its working again!
Logs said: Unable to get api key: TypeError: Cannot read properties of undefined (reading 'includes') Something is going wrong with the reading of the config files, imho.

zhanghaoranas commented 1 year ago

I have encountered the same problem

marlberm2014 commented 1 year ago

I'm getting it too. I downgraded to 24.0.7 and its working again! Logs said: Unable to get api key: TypeError: Cannot read properties of undefined (reading 'includes') Something is going wrong with the reading of the config files, imho.

This one works, thanks.

HanJaeJoon commented 1 year ago

I've also encountered this. downgrading to 24.0.7 works for me. thank you DavoDC.

DavoDC commented 1 year ago

This one works, thanks.

You're welcome 😊

lukethacoder commented 1 year ago

https://github.com/wakatime/wakatime-cli/issues/660

would say its almost related to this... but doesn't look like any antivirus is flagging any files. Must be something else.

Looks like some code was accidentally removed? https://github.com/wakatime/vscode-wakatime/pull/337 should fix things.

juliamuiruri4 commented 1 year ago

Encountering the same issue this morning and being forced to disable

manthanank commented 1 year ago

Same here, but by downgrading to to 24.0.7 it's working.

CelebMunyiri commented 1 year ago

downgrading it to 24.0.7 works for me

mason369 commented 1 year ago

The previous usage was fine, but now there's always a pop-up prompt. gif

FywOoie commented 1 year ago

downgrading to 24.0.7 works for me as well

alanhamlett commented 1 year ago

Fixed with c0c9356fe7fed89437729dc79d8d9c4bdf8609c1 and released in v24.0.10.

Aditya7997 commented 4 months ago

Removing wakatime extension from the VS code worked for me.