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.21k stars 134 forks source link

Wakatime VSC error -4058 #333

Open mikeyfe6 opened 1 year ago

mikeyfe6 commented 1 year ago

Hi!

I have this issue with Wakatime and Visual Studio Code. It used to work perfectly.. But now the Wakatime extension stops after initializing and gives me a wakatime error;

Is it a option to re-install VSC? i've already reinstalled the wakatime extension.. no success...

Screenshot (20)

Thanks in advance!

GreenJ84 commented 1 year ago

Getting the same thing. It just dropped off two days ago for me. Have tried installing the extension and even refreshed a new api key.

alanhamlett commented 1 year ago

Maybe this was due to the GitHub outage a while back? We download wakatime-cli directly from GitHub releases. Can you try deleting the folder ~/.wakatime/ and restarting vscode?

alanhamlett commented 1 year ago

Also, try deleting ~/.wakatime-internal.cfg because that keeps the release version that's downloaded when GitHub says there aren't any new releases.

mikeyfe6 commented 1 year ago

@alanhamlett Still the same problem tho.. its gives me a cfg file with cli_version v1.70.1 and the last modified date in it.

Also the wakatime-cli-windows-amd64.exe file in the .wakatime folder doesnt run if i click it. Similar on my mac i can run it tho by clicking on the wakatime-cli-darwin-amd64.exec file and it runs smoothly, so i guess the .exe file has some issues (?)

alanhamlett commented 1 year ago

What happens if you run it from a terminal with:

wakatime-cli-windows-amd64.exe --version

mikeyfe6 commented 1 year ago

@alanhamlett this is the output; 'wakatime-cli-windows-amd64.exe' is not recognized as an internal or external command, operable program or batch file.

alanhamlett commented 1 year ago

Looks like it's not in your CWD path. You might need to add .\ before the program or might need to cd into ~/.wakatime/ before running the command.

mikeyfe6 commented 1 year ago

This is the response i get from my terminal;

PS: with the latest update (v24.0.9) i hoped it would be solved, but now the issue is that its keeps asking me for my API key, even if i filled it in correctly. The popup keeps showing up very 5 min appr..

I went over the steps again with deleting the ~/.wakatime-internal.cfg file and the ~/.wakatime/ folder. One thing changed is that the config file is now generated in the folder instead of the root of C:\Users\mfransman..

Screenshot (56)