-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Sign in with Google temporarily disabled for this app #533
Comments
Same |
same |
Only Dev can do the verification, specifically the GDrive Dev (Petter Rasmussen). So this tool unusable until it's verification process completes. |
Same here! |
Same here |
same here |
update, actually this like worked for me |
Same here |
Same |
No need to compile from source, just create service account in google console and use |
@yarkm13 can you help us with this? Any further information on how to make it works are very appreciated. |
@yarkm13 @quangpham
Now the important bits is your Service Account have their own Google Drive space. This mean that if you upload file, it won't show up in your drive. To workaround this, your account need to create a shared folder with your service account email as the editor. See this Stackoverflow discussion: https://stackoverflow.com/questions/45492703/google-drive-api-oauth-and-service-account Now to get the folder ID you can follow the tips from this blog: https://ploi.io/documentation/mysql/where-do-i-get-google-drive-folder-id IMPORTANT NOTE: There's an unmerged fix (#331) for changing ownership of files. For now GDrive util will throw error: 'Failed to share file: googleapi: Error 403: The transferOwnership parameter must be enabled when the permission role is 'owner'., forbidden' Hope this helps. |
@quangpham i think @nathanaelytj has explained completely. I was done the same |
My personal Google account have much more Google Drive storage limit than the Service Account Free Google Drive space (16GB), is there any solution to link my personal account by Service Account OAuth? |
Same issue. Any ETA when this is going to get fixed? |
Duplicate of: #506 |
Issue still there. App still useless. The service account doesn't have enough space. |
@JurajMa create directory in your main account and share it with service account email address. Now you need to point your service account to work with that directory. |
if follow this step, but command gdrive --service-account will throw an error like this |
same issue as @hikmawanaz |
same problem |
@nathanaelytj UPD: I have several accounts, and when I clicked "set up consent screen" for some reason google switched my account, after switching back everything works. |
@hikmawanaz I found that the brew installation didn't have the Once you'd uploaded files using a service account, how do you then pass ownership to your normal user account? I find it a bit odd having the owner and a service account. |
@joemidi first create dir in your service account
get object id of that dir
and grant permissions for your root account to that dir
Dont forget to setup sync to that dir, not in root
Bonus: wou will have extra 15Gb space on Google Drive (data stored by service account will not count in your root account) |
But doesn't this mean the folder I created is owned by the service account? |
@joemidi according to gdrive help you also can grant
|
@joemidi also i think you can go opposite way: create directory in your root account and than grant permissions to it for service account. But I haven't tested that |
@yarkm13 Yes, I ended up doing it this way, you can just share the folder via the web UI, the folder is my own ownership but each file is created by the service account. I did notice that
|
I forked this repository to https://github.com/ntechp/gdrive, merge gdrive-org#513, gdrive-org#270, gdrive-org#331 All is in this non-official release note: https://github.com/ntechp/gdrive/releases/tag/2.1.0-0.0.1 This fork temporarily fixes 3 probs:
I do hope someone maintain this repository, merge all the fixes (because some of the issues already fixed by community), and update the release. |
Thanks for this useful guide ! |
For my case, each service account is limited to 16GB only. So I wasn't entitled to the unlimited quota of the Gsuite account. |
Thanks, it solved my problem |
This method do help me. Thank you very much! |
Anything I missed? |
I feel overwhelmed by all the steps required to make this work... and all the reports of failure just make me postpone it even more, mainly considering I can't even compile it. The "go" compiler wont accept anything I type, yes I am a "go noob", what is the "go" compile command? as the one at readme.md wont work :(, yes I installed the go-lang package, I am on linux. So my question is, Why not just fix this: I mean, why not we join forces and beg google to verify this app!!! I mean, this app is great and should work "out of the box" and not require all these steps from noobs like me :/. |
@AquariusPower I gave up on gdrive and switched to rclone. |
@skeith EDIT: I end up using this: https://github.com/odeke-em/drive#initializing, the best thing on it is that if you got very low quota (like 100MB/day) it will not try to synchronize, so you can just upload specific changes and use as little as possible of that horrible quota :) |
It's not a google problem. The developer needs to initiate the verification. The result is that "join forces" boils down to someone forking the project (several have done so already) and paying the fee. Without someone paying the fee, you'll have to do everything to "become the developer" yourself (because you don't have to pay the fee if you're only using it yourself) |
How much is the fee 😓 |
Offering my few cents
And requesting verification is free. The problem lies in creating App Home Page, App Privacy Policy, App Term of Service (App Term of Service marked as Optional by Google). Those legal things need to be present and tailored to fulfill Google Requirements before the app marked as verified.
|
Try backuptogoogle to compile gdrive with your own Google credential and auto backup on your server. |
I'm still unable to get the I Still get the error No valid arguments given, use 'gdrive help' to see available commands |
I believe this issue has been fixed 2021-05-28 and should be closed. Quoting from the current README:
|
When I try to login to the link given by
gdrive list
, I'm brought to a page statingThe text was updated successfully, but these errors were encountered: