-
Notifications
You must be signed in to change notification settings - Fork 216
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
Unable to retrieve calendars; poor UX when required Google scopes not authorised. #1937
Comments
The big problem was that OGCS uninstall left a folder in the roaming folder
that remembered the failed Google authentication and therefore failed after
a reinstall. I chanced upon that folder and deleted it and then
re-authenticated and it worked.
…On Sat, Aug 17, 2024 at 6:51 PM Paul Woolcock ***@***.***> wrote:
Oh dear, it looks like Google have changed the authentication process and
the required permission is not unchecked by default 🙁
You need to tick the box to give OGCS the required access:-
image.png (view on web)
<https://github.com/user-attachments/assets/f80ecc14-8fb3-4dbd-90e7-6cc0fee85916>
However, I will now see if:-
- I can make OGCS handle it better when the required permissions are
not present
- the permissions can be refined better to not require share and
delete calendars (as OGCS doesn't need or do anything with that permission!)
—
Reply to this email directly, view it on GitHub
<#1937 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD5DCMQCCKWK47ICZ3DJKD3ZR6ERZAVCNFSM6AAAAABMVNKOF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHEZDMMRRGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I'm also running into this issue but cannot find the folder in Roaming that @galexmay mentions. Any memory of what the folder was called or thoughts about what else I might do? |
The folder was/is C:\Users\[username]\AppData\Roaming\Outlook Google
Calendar Sync, I think. You have to switch on the view of hidden items, I
think.
…On Wed, Aug 21, 2024 at 6:15 PM Katie Hoemann ***@***.***> wrote:
I'm also running into this issue but cannot find the folder in Roaming
that @galexmay <https://github.com/galexmay> mentions. Any memory of what
the folder was called or thoughts about what else I might do?
—
Reply to this email directly, view it on GitHub
<#1937 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD5DCMSFWSZLIKOKYN5TSDTZSTDMJAVCNFSM6AAAAABMVNKOF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBSGU4DOMJTG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ok, this worked for me. I disconnected the google account and restarted the app, then when it asked to reconnect, i got the checkbox option and then synced. seems to work now |
📦 OK, this hotfix v2.11.0.2.zip (see instructions for applying) should at least resolve the proper deletion of the token file, thus making it easier to then authorise the required permissions. Meanwhile, I'll work on improving behaviour with insufficient scopes... |
This comment was marked as outdated.
This comment was marked as outdated.
📦 And now hotfix v2.11.0.6.zip (see instructions for applying) should behave better when insufficient permissions are granted to OGCS. Please let me know how it goes! |
User outside of GitHub has confirmed success with hotfix. |
I tried to install on my new computer. Despite your website talking about various versions, there only seems to be the option to download the 2.11.0-beta version so that is what I downloaded. In installed that version. I set up the Outlook folder and then connected my gmail account. I then got the following error messages. I tried to disconnect the account but when I went to reconnect it, it was already chosen and I immediately got the same error message. I tried uninstalling and reinstalling but nothing changed. In fact, the settings still appeared to be there despite the uninstall. What do I do now?
OGCS Version: 2.11.0-beta
Edition: Installed
Sync Direction: didn't get that far
Bug Description
see above
Steps to Reproduce the Issue
see above
Any other information
📎 Attach your
OGcalsync.log
file. attachedOGcalsync.log
The text was updated successfully, but these errors were encountered: