Closed bulletproof2k closed 2 years ago
After enabling debug mode what output do you see in your Sublime Console window after reloading Sublime (ctrl+r)?
[WakaTime] [INFO] Initializing WakaTime plugin v11.0.5
[WakaTime] [INFO] Current wakatime-cli version is v1.45.3
[WakaTime] [INFO] Checking for updates to wakatime-cli...
[WakaTime] [DEBUG] GitHub API Response 304
[WakaTime] [INFO] wakatime-cli is up to date.
[WakaTime] [DEBUG] C:\Users\victo\.wakatime\wakatime-cli-windows-amd64.exe --today --key XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX237e --plugin sublime/4126 sublime-wakatime/11.0.5 --verbose
[WakaTime] [DEBUG] wakatime-core today exited with status: 104
104
exit code means an authentication error, usually because your api key is invalid or because of a proxy in-between your machine and the WakaTime API. Does the key in your ~/.wakatime.cfg
file match your api key here?
Actually, Sublime is unique where sublime-wakatime uses the .sublime-settings
file for your api key so you should check there instead of the common cfg file.
alanhamlett I think my problem is solved. If this is a WakaTime display:
But I used the Api Key for the WakaTime from this site:
If all of the above is confirmed, then I close this topic, thank you for your help Alan!
Also, remember to turn off debug mode now.
@alanhamlett Hello Alan!
Today I ran into this problem:
And after a while:
Debug mode is enabled:
And the plugin status is OK.
Sorry for the bad English.