Stopped working even if logged in

Started getting the following error:

1618161793982 DEBUG  [TextGrammarCheckHost] (66696c) Hosting file:///Volumes/Workspace/Writing/Draft.dev/in-progress/Achieving%20Repeatability%20in%20Continuous%20Integration/Request.md
(node:392999) UnhandledPromiseRejectionWarning: Error: Socket connection failed: NOT_AUTHORIZED
    at GrammarlyClient._connect (/home/amacgregor/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:38903:19)
    at GrammarlyClient._queueOrSend (/home/amacgregor/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:38978:18)
    at /home/amacgregor/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:38876:18
    at new Promise (<anonymous>)
    at GrammarlyClient.send (/home/amacgregor/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:38874:16)
    at GrammarlyClient.start (/home/amacgregor/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:39160:21)
    at GrammarlyClient.onConnection [as _onConnection] (/home/amacgregor/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:39809:32)
(node:392999) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)

[znck]

The NOT_AUTHORIZED error code occurs when access token received from OAuth has expired. I haven’t implemented token deletion or refreshing. However, as a workaround you can:

1. Logout using Grammarly: Logout from grammarly.com
2. Reload or Restart VS Code
3. Login using Grammarly: Login to grammarly.com

I don’t have bandwidth to fix this issue right now but I am open to PRs.

[znck]

Nice catch. I am not checking token for expiration. Will try to fix.