search

vitalif / grive2

Google Drive client with support for new Drive REST API and partial sync
http://yourcmc.ru/wiki/Grive2
GNU General Public License v2.0
1.52k stars 140 forks source link

Error when authenticating: This app is blocked #404

Open markusb opened 3 months ago

markusb commented 3 months ago

When I vists the URL given with 'grive -a' I get the following error message:

This app is blocked

This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access.

Predbo commented 2 months ago

same here

funny0facer commented 1 month ago

did you read and follow this information: https://github.com/vitalif/grive2#different-oauth2-client-to-workaround-over-quota-and-google-approval-issues ?

ChooChooAl commented 2 weeks ago

The steps seem to have changed? I just attempted the steps, and the 2nd item in step 5 was not there (CLI) and from there on it seemed to deviate a bit. I had to use my email as support and author at one stage. But I did get a download file. Per the site, I should wait for 5 minutes for it to work.

galenthurber commented 2 weeks ago

same here will follow thread

ChooChooAl commented 2 weeks ago

I did fill the forms and I do still have a "reviewing" note on my client so I guess they are still reviewing.

funny0facer commented 1 week ago

The steps seem to have changed, but I did not have any problem to create a new token. Here are the steps I did in form of pictures: Oauth

ChooChooAl commented 1 week ago

So how do I use this? In reading it looks like all I need to do is: cd grive -a --id --secret

But it doesn't seem to work. I still get the 'click on link and authenticate' prompt.

funny0facer commented 1 week ago

you have to provide values for --id and --secret. Then click on the link and approve the access. You might need to click on "advanced" or "extended". My german screenshot show you how it should look like:

screenshot

The name of the app should be identical to the name within the google API settings:

grafik

ChooChooAl commented 1 week ago

Are you saying that I have to rename /bin/grive2 to /bin/rclone and then call this ?
rclone -a (etc) This is what I see Screenshot from 2024-11-20 13-46-47

ChooChooAl commented 1 week ago

I renamed the app in credentials to grive2z (I'm running this on Zorin OS. I'll need a way to know which 'grive' I'm using), and I now get this message that says the approval has not completed yet. So I can't go any further.
Screenshot from 2024-11-20 14-00-04

funny0facer commented 1 week ago

you do not need to rename the actual binary. I just created a new project and changed to the new layout to check what might gone wrong on your side. Did you maybe "publish" your app? You want your app either "internal" oder "external testing" Screenshot_20241120_222231

Screenshot_20241120_222257

No verification of the App should be necessary

ChooChooAl commented 1 week ago

Do I publish? I did not.
Mine is set to testing external. Yet it still doesn't authorize.
Can't do internal. I'm not a google workplace user (per the pop up). When I do the grive -a thing, I get the link to open a browser and I have to log in as myself with my account. But it stops there with the "app is waiting in review" message.

ChooChooAl commented 1 week ago

Not sure if I did this right. I added my self to the user testing list. Complete email address. I then went back and did the grive -a. I use firefox and this time I got a error message that the authentication could not continue, and reminded me FF will not authenticate sometimes correctly. Either an add-on? Anyway I copied the link and pasted it in Edge and the authentication went through okay. I'm downloading files now. Hopefully I haven't mucked up the other OS I use.

funny0facer commented 1 week ago

Congratulations, sounds great! I did not have an issue on firefox to authenticate, but yes, maybe an addon.