Invalid API key
See original GitHub issueI am having no luck getting up and running with the extension on VSCodium Version: 1.73.1 Contents of ~/.wakatime.cfg are…
[settings]
debug = true
api_key = waka_key
I’ve tried reinstalling the extension and even nuked my account and created a new one but I only see a message saying Invalid API key…check wakatime.com/settings
Console returns
workbench.desktop.main.js:87 [Extension Host] [WakaTime][WARN] Unable to get api key: Error: could not read ~/.wakatime.cfg
Is this file supposed to be written at install? In my case I have to create it and still the same issue. I know this issue is duplicated and closed, but no solutions are available in older issues.
~/.wakatime.log file contents…
{“caller”:“cmd/run.go:81”,“func”:“cmd.Run”,“level”:“debug”,“message”:“command: config-read”,“now”:“2022-12-07T23:17:27-08:00”,“os/arch”:“darwin/arm64”,“version”:“v1.60.1”} {“caller”:“cmd/run.go:128”,“func”:“cmd.Run”,“level”:“warning”,“message”:“one of the following parameters has to be provided: --config-read, --config-write, --entity, --offline-count, --print-offline-heartbeats, --sync-offline-activity, --today, --today-goal, --useragent, --version”,“now”:“2022-12-07T23:17:59-08:00”,“os/arch”:“darwin/arm64”,“version”:“v1.60.1”} {“caller”:“cmd/run.go:128”,“func”:“cmd.Run”,“level”:“warning”,“message”:“one of the following parameters has to be provided: --config-read, --config-write, --entity, --offline-count, --print-offline-heartbeats, --sync-offline-activity, --today, --today-goal, --useragent, --version”,“now”:“2022-12-07T23:18:25-08:00”,“os/arch”:“darwin/arm64”,“version”:“v1.60.1”}
Issue Analytics
- State:
- Created 9 months ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top GitHub Comments
It should work with the prefix too now.
Thanks for the FB, Alan. I got the thing to work finally after a clean environment rebuild, and minimal configuration with an API key without the
waka_
prefix.