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

Unable to login #894

Open
DirkNie opened this issue Oct 31, 2024 · 4 comments
Open

Unable to login #894

DirkNie opened this issue Oct 31, 2024 · 4 comments

Comments

@DirkNie
Copy link

DirkNie commented Oct 31, 2024

Hi,
I have done the installation and then the "Usage" part. But I get an login error
grafik

Is it possible to become an developer tester to get access?
Or is there an actual issue for that behavior?
I found an hint to switch to production. But how to do?
TIA Dirk

google-drive-ocamlfuse -version
google-drive-ocamlfuse, version 0.7.32
Copyright (C) 2012-2024 Alessandro Strada
License MIT

System:
Kernel: 6.8.0-48-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 clocksource: tsc
Desktop: Cinnamon v: 6.2.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.2.0 vt: 7 dm: LightDM v: 1.30.0
Distro: Linux Mint 22 Wilma base: Ubuntu 24.04 noble

@astrada
Copy link
Owner

astrada commented Nov 1, 2024

I'm sorry but Google changed the authorization process so now you have to create your own credentials: https://github.com/astrada/google-drive-ocamlfuse/wiki/Authorization

@DirkNie
Copy link
Author

DirkNie commented Nov 1, 2024

Hello astrada,
I do not understand your comment. I created my own credentials in Google cloud. I generated an project, activate the Google Drive API and then the OAuth 2.0-Client-ID. I get the message above when I run the described command:

$ google-drive-ocamlfuse -id 12345678.apps.googleusercontent.com -secret abcde12345

Naturally with my credentials.
A few minutes later I get that message:
Error: Cannot retrieve verification code: Timeout expired

TIA Dirk

@astrada
Copy link
Owner

astrada commented Nov 1, 2024

Ok, sorry, maybe you added scopes to your oauth application? If so, you should remove them and I think the error should go.

@DirkNie
Copy link
Author

DirkNie commented Nov 1, 2024

Hello astrada,
I found the problem. It was the set to productive. I haven't found that last time.
One hint from my side, your link to the "how to set to productive" is dead. Would be nice you can repair.

cu Dirk

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

2 participants