Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Required parameter is missing: response_type #240

Open
mankoff opened this issue Jun 2, 2023 · 4 comments
Open

Required parameter is missing: response_type #240

mankoff opened this issue Jun 2, 2023 · 4 comments

Comments

@mankoff
Copy link

mankoff commented Jun 2, 2023

I'm using the latest master commit and I think I've followed the https://github.com/kidd/org-gcal.el#Installation steps correctly.

When I run org-gcal-fetch my browser opens a window and displays an error message:

Access blocked: Authorization Error
[email protected]
Required parameter is missing: response_type
If you are a developer of this app, see
Error 400: invalid_request

I'm not seeing Required parameter is missing: response_type mentioned in any previous issues.

@telotortium
Copy link
Collaborator

@mankoff Could you let me know if you've customized any org-gcal- or oauth2-auto- or plstore- variable? What are their values (redact any sensitive info)?

@mankoff
Copy link
Author

mankoff commented Jun 5, 2023

I've set org-gcal-client-id and org-gcal-client-secret to the values from the Google API page.

I have not set oauth2-auto or plstore to anything. The manual makes it seem like that's a convenience issue so you don't need to enter your password too often. I was going to solve that later.

@mankoff
Copy link
Author

mankoff commented Jun 5, 2023

More specifically,

  (setq org-gcal-client-id "nnnnnnnn-nnnnnnnnn.apps.googleusercontent.com"
	org-gcal-client-secret "foo-bar--baz"
	org-gcal-fetch-file-alist '(("https://calendar.google.com/calendar/ical/__email__/__private_string__/basic.ics" .  "/path/to/local.org")))

@Wacken
Copy link

Wacken commented Aug 14, 2023

I had the same issue. I'm not sure which steps are needed, but I solved this problem by adding myself as a test user on the OAuth consent screen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants