-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
<HttpError 404 when requesting https://www.googleapis.com/drive/v2/files/1CwhDy8SBXaInfY2WdWfgK1wROeUNuesC?alt=json returned "File not found: 1CwhDy8SBXaInfY2WdWfgK1wROeUNuesC"> #1186
Comments
Hi @bc060400164 , Please can you share some sample code to see if this issue can be reproduced? As we haven't released a new version of this client library recently, my initial thought is that you may need to file a bug directly with the upstream API using these steps. |
Dear parthea file_id = '1CwhDy8SBXaInfY2WdWfgK1wROeUNuesC' Read file as panda dataframeimport pandas as pd |
I'm having a similar issue and I suspect it is an issue on Google's side but I haven't figured out anything yet. I have a Google Cloud Platform service account with domain-wide delegation enabled and Until recently the server using this account has not had any problems connecting to three different shared drives, creating folders underneath them, or returning a folder's contents. Now, the server is getting 404s when trying to create folders underneath a drive or list a directory's contents under the drive. The drive and those folders definitely exist - I can access them on the Google Drive web page. That leads me to believe this is a permissions issue but I have not found anything on my search. This is the code for creating a folder underneath a drive that now returns a 404 and tells me the drive does not exist: file_metadata = {
'name': name,
'mimeType': 'application/vnd.google-apps.folder',
'parents': [drive_id]
}
file = service.files().create(body=file_metadata, fields='id', supportsAllDrives=True).execute() I'm not sure exactly when this started happening but it was brought to my attention in the past few weeks. I don't think there is anything that this package can do to help out because it is just forwarding on Google's response but maybe someone can point us in the right direction. Edit: I forgot to mention that this is only an issue for 2 of the 3 drives this server connects to. One still works properly. And Google's documentation on this is not helpful: https://developers.google.com/drive/api/v3/handle-errors#resolve_a_404_error_file_not_found_fileid I am using version I have posted this question to stackoverflow as well: https://stackoverflow.com/questions/67186894/shared-google-drive-suddenly-returning-404-with-service-account |
I ended up figuring out my issue: https://stackoverflow.com/a/67199941/5404586 |
I'm going to close this issue as obsolete but please feel free to re-open it if the issue still exists. |
Hello! Was there any solution to this issue? I am currently running into a problem where my service account has access to a shared drive, I can get a list of the contents, but when I try to copy a file inside said folder I get the following error:
I know the file exists since when I do :
I indeed get a list of files. Using the output from this I tried making a copy of a file to no avail:
any help will be greatly appreciated! |
After some days i start getting the error. To solve the issue i need the other Gmail account. Why its happening? Any comment or guideline. File is there in drive with same link. After one week it starts giving the error.
The text was updated successfully, but these errors were encountered: