search

kidd / org-gcal.el

Org sync with Google Calendar. (active maintained project as of 2019-11-06)
432 stars 47 forks source link

"Authorization Error - Error 400: invalid_request" #195

Open jzohrab opened 2 years ago

jzohrab commented 2 years ago

Hi there, requesting set-up assistance, and if I can solve it I'll contribute some docs back.

org-gcal used to work, but has stopped. I updated the installation to this repo (following https://melpa.org/#/org-gcal) and trying org-gcal-request-token gives me the following:

image

I created a new google project with the Calendar API as shown in the README. I believe I've done everything correctly.

I deleted the .org-gcal-token as suggested in https://github.com/kidd/org-gcal.el/issues/173, no effect.

When I run the request-token function, it shows the following in the minibuffer:

Please visit (if it doesn't open automatically): https://accounts.google.com/o/oauth2/auth?client_id=459054706968-8m53jnousbu20s39ne982a3264p38ep4.apps.googleusercontent.com&response_type=code&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar

going to that link also gives the same error screen.

Any thoughts? Cheers, jz

alvesmgabriel commented 2 years ago

I'm facing same issue after I moved from ivy to vertico on doom. My org-gcal settings stopped to work. The variables like org-gcal-client-id and org-gcal-client-secret don't load.If I load them manually the org-gcal gets the "rx '**' error" (#172).

alvesmgabriel commented 2 years ago

If I load them manually the org-gcal gets the "rx '**' error" (#172).

I've solved this with (unpin! org-gcal)

npit commented 2 years ago

Having the same issue on spacemacs.

alvesmgabriel commented 2 years ago

I moved from ivy to vertico on doom.

I found a command (require 'ivy) in my settings, the issue is not related to vertico. Did you add your email to the test users list in the OAuth Consent Screen?

philongphan commented 2 years ago

Seems like Google deprecated their OAuth flow, which is why we see this error message. Therefore the authentication method stopped working since 28.02.2022. https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#disallowed-oob

cwsteinbach commented 2 years ago

This issue is tracked in #191.