Error when authenticating: This app is blocked

[markusb]

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]

same here

[funny0facer]

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

[ChooChooAl]

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]

same here will follow thread

[ChooChooAl]

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

[funny0facer]

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:

[ChooChooAl]

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]

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:

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

[ChooChooAl]

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

[ChooChooAl]

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.

[funny0facer]

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"

No verification of the App should be necessary

[ChooChooAl]

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]

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]

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

[xSeekTruthx]

Just stopped working about 2 weeks ago. Got the new api and key, worked for a week, then stopped again. Did again, worked for a week then stopped. Am I missing something?

[ChooChooAl]

I'm having the same issue with my 2 systems I'm trying this with. They are test and I don't use them but once a week maybe.
I have a shell script the does the grive -a --etc to do the password and name to restart it. It works the the duration of my visit but when I return I have to do it again. I don't have to make a new auth thank goodness.

[xSeekTruthx]

That's cool! Could you post it here? I could just cron schedule that. Good enough for me 😀

…

On Sun, Dec 8, 2024 at 4:45 PM Alan ***@***.***> wrote: I'm having the same issue with my 2 systems I'm trying this with. They are test and I don't use them but once a week maybe. I have a shell script the does the grive -a --etc to do the password and name to restart it. It works the the duration of my visit but when I return I have to do it again. I don't have to make a new auth thank goodness. — Reply to this email directly, view it on GitHub <#404 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AENSVWOAE4R2LKIJXBOZ4S32ES4W3AVCNFSM6AAAAABL7E6WSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRWGM4TMMZVGU> . You are receiving this because you commented.Message ID: ***@***.***>

[ChooChooAl]

How you launch this I'll leave it to you. Please test this in the command line. I just added the 2>.... part and haven't had to test it.
My update seems to work fine today.
Shell script as follows, note that I make a log file in my grive folder. Folder named after the grive command duh! :

#!/bin/bash
echo "

Are you sure you want to reset Google Drive?"
echo
read -n1 -r -p "$(echo -en "\e[1;93m")Press any key to continue...$(echo -en "\e[0m")" key

if [ $key = "y" ]
then
cd ~/grive
rm .grive
grive -a --id "put id here" --secret "put secret here" 2>&1 |tee -a ${HOME}/grive/update.log
fi

[xSeekTruthx]

Thank you! I will try this soon and report back.

[novazur972]

I have a shell script the does the grive -a --etc to do the password and name to restart it.

I have to do it about every 10 days. But sadly impossible to script it because I have to clic on the link provided then choose account in the browser.

[galenthurber]

I've given up on Google Drive, they truncated nearly 200 files of mine, it took nearly 2 months to get most of the files back.
Too untrustworthy unreliable

[novazur972]

I've given up on Google Drive, they truncated nearly 200 files of mine, it took nearly 2 months to get most of the files back. Too untrustworthy unreliable

I agree. I will also stop with it quickly.