-
Notifications
You must be signed in to change notification settings - Fork 113
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
org-gcal-sync no longer working - change in Google's API program? #117
Comments
+1 |
Same here |
I don't know if this is the same issue, but I get the message: Could not contact remote service. Please check your network connectivity (a few months ago it worked fine |
Looks like they changed the API changed and that org-gcal-sync needs to be updated to support the change. |
same here |
I was able to get org-gcal-sync to work, but I'm unsure if billing information is required since I have it set-up for Google compute. Try searching for calendar here, and then set-up credentials again. |
@AlexLewandowski Awesome, I genuinely thought this was dead. A few questions:
Thanks in advance! |
Hi, I still don't get it working (partly due to the outdated documentation on google projects). |
I hadn't used org-gcal.el for a quite some time and when I recently tried to set it up again, I thought maybe I was running into an issue with possibly changed APIs as described here. However, after reading through comments here and on reddit, I eventually found this helpful report from @dominic998 in the commends on another issue, which solved my problem:
Cross-posting here in the hopes that it might help save time for someone else whose initial troubleshooting also brings them to this open issue. If anything could be classified as a bug in my case it might just be this (from same comment above):
Note: I did notice some lines in The messages looked something like this (I've redacted anything that looked at all sensitive or unique):
|
Re-reading the README more carefully now, I also noticed that there is an
Having a hook to run that automatically, if needed ,before |
The community left this repo for https://github.com/kidd/org-gcal.el/ And that repo is what MELPA currently references |
Hi everyone! This repository is obsolete - the actively developed fork is now https://github.com/kidd/org-gcal.el, which is also the "org-gcal.el" on MELPA (see #115). I'm one of the maintainers of https://github.com/kidd/org-gcal.el. I can't directly close issues or PRs on this repo, but please download https://github.com/kidd/org-gcal.el and see if your issue or PR is still applicable. If so, open an issue or PR on https://github.com/kidd/org-gcal.el. In any case, you should close your issue or PR in this repo. |
I noticed recently that org-gcal-sync has not been working as the minibuffer just sits trying to connect to www.googleapis.com:443.
I then went to the Google Developers page where I had my creds setup and couldn't find them anywhere and then noticed that they have a new Google Cloud Key Management section where they want you to setup a billing account.
Is this what we have to do to get syncing to function again?
The text was updated successfully, but these errors were encountered: