-
Notifications
You must be signed in to change notification settings - Fork 215
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
Cannot retrieve google calendar #1984
Comments
I am having the same issue on a new Win 11 PC. I'm also using v2.11.0.0. |
I deleted everything in the folder where the log file is stored and I was able to reconnect the google account and select the option to see/edit/share On the help screen at the bottom under trouble shooting, click the log file and it will open the folder in windows. Delete all that and it should work. |
That solved the problem! Thank you! |
Thank you, but in which folder I can find the log files? |
As in mister-gem's comment, at the bottom of the help tab, you can find a link to "OGcalsync.log file" |
Thank you so much, Finally I found it and worked! |
OGCS Version: v2.11.0.0
Edition: Installed
Sync Direction: O<->G
Bug Description
I added google account and attempted to retrieve, it shows connected account, but gives error:
Authenticating with Google
Preparing to authenticate with Google.
Handshake successful.
Unable to get the list of Google calendars. The following error occurred:
Request had insufficient authentication scopes. [403=Forbidden]
Unable to get the list of Google calendars. The following error occurred:
Request had insufficient authentication scopes. [403=Forbidden]
Unable to get the list of Google calendars. The following error occurred:
Request had insufficient authentication scopes. [403=Forbidden]
Steps to Reproduce the Issue
OGcalsync.log
I have tried disconnecting the google account and starting over. Even uninstalled the app and tried again, but the google account was already there without logging in again. Not sure how to clear it out and start fresh.
The text was updated successfully, but these errors were encountered: