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

deferred error "oauth2-auto: Unknown provider: org-gcal" #209

Closed
mfuchs1 opened this issue Nov 20, 2022 · 5 comments
Closed

deferred error "oauth2-auto: Unknown provider: org-gcal" #209

mfuchs1 opened this issue Nov 20, 2022 · 5 comments

Comments

@mfuchs1
Copy link

mfuchs1 commented Nov 20, 2022

Hello,

org-gcal was working fine until now.
I've updated org-gcal via melpa and I got this error message when running org-gcal-fetch or org-gcal-sync:

deferred error : (error "oauth2-auto: Unknown provider: org-gcal")

I'm using GNU Emacs 28.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.34, cairo version 1.17.6)
of 2022-09-12

OS: Manjaro KDE 22.0.0

Thanks for your help.

@telenieko
Copy link

Try calling (org-gcal-reload-client-id-secret) after setting the org-gcal-client-** variables.

@mfuchs1
Copy link
Author

mfuchs1 commented Nov 20, 2022

Yes, thank you! That did the trick. org-gcal is working again. I can fetch events from google calendar and post events from org-mode to google. It's even better - there are no

"Received HTTP 412 ETag stale for will averwirte this entry with event from server"

messages anymore. Thank you. I think you can close this issue.

@telotortium
Copy link
Collaborator

@mfuchs1 Did you see the warning "org-gcal: must set ‘org-gcal-client-id’ and ‘org-gcal-client-secret’ for this package to work. Please run ‘org-gcal-reload-client-id-secret’ after setting these variables."? I thought I detected this case here.

@mfuchs1
Copy link
Author

mfuchs1 commented Nov 20, 2022

@mfuchs1 Did you see the warning "org-gcal: must set ‘org-gcal-client-id’ and ‘org-gcal-client-secret’ for this package to work. Please run ‘org-gcal-reload-client-id-secret’ after setting these variables."? I thought I detected this case here.

No, I didn't see this warning - I'm sorry. I've set the ‘org-gcal-client-id’ and ‘org-gcal-client-secret’ in my init.el - already before this new update. The ‘org-gcal-reload-client-id-secret’ resolved the issue.

@telotortium
Copy link
Collaborator

That's interesting, because with both ‘org-gcal-client-id’ and ‘org-gcal-client-secret’ set, ‘org-gcal-reload-client-id-secret’ should have automatically been called when the package was loaded (I just tested it, and I can confirm ‘org-gcal-reload-client-id-secret’ was called). Perhaps Melpa upgrades don't automatically re-evaluate the package somehow? I tend to upgrade in one of two ways, since I use Doom Emacs:

  1. Doom downloads and recompiles the files. Then, I usually restart Emacs.
  2. I make a change to org-gcal while developing and then call eval-buffer.

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