grammarly icon indicating copy to clipboard operation
grammarly copied to clipboard

Grammarly login shows an error

Open martinszeltins opened this issue 2 years ago • 18 comments

I am following the instructions to log into Grammarly on VSCode but I am getting this error (Linux, Ubuntu 20.04)

image

Request $/handleOAuthCallbackUri failed with message: Minified error #8: See https://developer.grammarly.com/docs/error-explainer...

Grammarly account or premium

Run grammarly.login or Grammarly: Login / Connect your account command to connect your Grammarly account.
Run grammarly.logout or Grammarly: Log out to disconnect your account.

I ran grammarly.login then I was redirected to the Grammarly login page and then I clicked on the "Continue" button and then this error showed up in my VSCode.

martinszeltins avatar Mar 01 '23 06:03 martinszeltins

Same here.

gfraiteur avatar Mar 02 '23 17:03 gfraiteur

+1 ... MacOS: shift+cmd+p, select "Login/connect to your account", follow the instructions and get the error.

nicofranzp avatar Mar 02 '23 17:03 nicofranzp

Nothing in the output console, either

eadgbear avatar Mar 02 '23 17:03 eadgbear

Same here.

ZhijieFan avatar Mar 03 '23 07:03 ZhijieFan

Same here.

tmogoa avatar Mar 03 '23 09:03 tmogoa

Same here.

I switched to the pre-release version and now it works.

tmogoa avatar Mar 03 '23 09:03 tmogoa

Same here.

I switched to the pre-release version and now it works.

Tried pre-release. No error this time but still not logged in.

chienhsiang-hung avatar Mar 06 '23 05:03 chienhsiang-hung

+1

Raaghu avatar Mar 08 '23 09:03 Raaghu

With the pre-release version, I get the following error when I shift+p - Check Text

Ready!
[Error - 5:03:50 PM] Server initialization failed.
Error: Connection got disposed.
    at Object.dispose (c:\Users\DummyUser\.vscode\extensions\node_modules\.pnpm\[email protected]\node_modules\vscode-jsonrpc\lib\common\connection.js:1044:27)
    at Object.dispose (c:\Users\DummyUser\.vscode\extensions\node_modules\.pnpm\[email protected]\node_modules\vscode-languageclient\lib\common\client.js:73:35)
    at c:\Users\DummyUser\.vscode\extensions\node_modules\.pnpm\[email protected]\node_modules\vscode-languageclient\lib\common\client.js:2320:28
[Error - 5:03:50 PM] Starting client failed
Error: Connection got disposed.
    at Object.dispose (c:\Users\DummyUser\.vscode\extensions\node_modules\.pnpm\[email protected]\node_modules\vscode-jsonrpc\lib\common\connection.js:1044:27)
    at Object.dispose (c:\Users\DummyUser\.vscode\extensions\node_modules\.pnpm\[email protected]\node_modules\vscode-languageclient\lib\common\client.js:73:35)
    at c:\Users\DummyUser\.vscode\extensions\node_modules\.pnpm\[email protected]\node_modules\vscode-languageclient\lib\common\client.js:2320:28

I cannot login and cannot check text. This happens on a fresh copy of VSCode with only this extension installed.

gragusa avatar Mar 08 '23 16:03 gragusa

I'm facing the same issue

qwezey avatar Mar 10 '23 00:03 qwezey

Same problem here. When I open the URL from the error reported by the VS Code Extension, Grammarly website shows this:

Invalid oauth callback url: vscode://znck.grammarly/auth/callback?windowId=1
Screenshot 2023-03-14 at 10 58 43

bajtos avatar Mar 14 '23 09:03 bajtos

This is the same as closed issue #323 . It seems to still be an issue.

rahji avatar Mar 14 '23 19:03 rahji

I can confirm that switching to pre-release fixes the issue.

spydx avatar Mar 15 '23 09:03 spydx

Yeah, I'm also having this issue.

Jimmy-Z avatar Mar 17 '23 13:03 Jimmy-Z

This is the same as closed issue #323 . It seems to still be an issue.

That issue is about getting Error #7. Most people here seem to get Error #8:

Invalid oauth callback url: vscode://znck.grammarly/auth/callback?windowId=1

MahdiNazemi avatar Mar 20 '23 01:03 MahdiNazemi

It looks like Grammarly has updated its APIs. I suspect this causes the login error.

One of the changes is

The oauth option is now specified at the top level as oauthRedirectUri.

MahdiNazemi avatar Mar 20 '23 18:03 MahdiNazemi

Not sure if anyone is working on this, but I made a branch with a possible implementation for updating Grammarly SDK to 2.x in hopes of solving this issue and possibly others.

rellyrell24 avatar Apr 01 '23 03:04 rellyrell24

Linking a useful workaround found by @crmelchior in a different (duplicate?) issue:

https://github.com/znck/grammarly/issues/350#issuecomment-1483848906

After switching to 0.18.0, successfully logging in and switching back to release (0.22.1) version, I'm still logged in and everything seems to work fine.

dqbd avatar Apr 10 '23 11:04 dqbd