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

"Something went wrong" google error when setting up oauth 2. #686

Open
hfytr opened this issue Jul 17, 2024 · 5 comments
Open

"Something went wrong" google error when setting up oauth 2. #686

hfytr opened this issue Jul 17, 2024 · 5 comments
Labels
bug needs-repro Reported issues which lack required details in order to reproduce

Comments

@hfytr
Copy link

hfytr commented Jul 17, 2024

So I am trying to set up gcalcli according to the README, but after selecting my account, and bypassing the "this app isn't verified", i get the message: "Something went wrong
Sorry, something went wrong there. Try again."

@dbarnett dbarnett added the needs-repro Reported issues which lack required details in order to reproduce label Aug 23, 2024
@dbarnett
Copy link
Collaborator

Can you still repro? If so, could you get a screenshot or any other available details?

@dbarnett dbarnett added the bug label Aug 23, 2024
@Tchou
Copy link

Tchou commented Sep 5, 2024

@hfytr are you by any chance using Firefox to open the OAuth url ? If so, could you try with Chrome ? I tried for a few days to get gcalcli to work on a Google Workspace account with every possible flavour of Internal/External/Test/Scopes/Api... to no avail. Until a switched to Chrome, based on a comment found on Stackoverflow, and with chrome it works 100% of the time. I thinks Firefox does not like going back to localhost:8080, for whatever reason.

@DaniloDjokic
Copy link

@hfytr I had a simillar issue with Firefox when trying to do the oauth. It turns out that my privacy focused extensions were messing up the URL as the application was still in "testing". You could try disabling the extensions or just doing the initial oauth with chrome

@kat0h
Copy link

kat0h commented Jan 4, 2025

I encountered the same issue on Firefox. I'm not sure which extension is causing it, but I was able to authenticate without any problems in a private tab.

@dbarnett
This issue seems both likely to occur and difficult to resolve. How about adding some information about it to docs/api-auth.md? If necessary, I can create a PR to add the documentation.

@DaniloDjokic
Copy link

@kat0h @dbarnett
If it means anything, the extension causing the issue was "Clear URLs". After disabling the extension the oauth passed successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs-repro Reported issues which lack required details in order to reproduce
Projects
None yet
Development

No branches or pull requests

5 participants