drive.files.insert failed with error: Not Being Used

[Alan Wells]

I'm getting an error:

API call to drive.files.insert failed with error: File not found: Not Being Used

What does that mean?

The code is trying to create a new file, so it's not looking for a file.  And if it's not looking for a file, then why would there be an error "File not found"  Unless, it's looking for a folder to put the file into, and the folder was not picked by the Google file picker?

[Michele Pisani]

Usually in this case the error message "404" (file does not exist) means that the user does not have read access to a file.

M

[Alan Wells]

I'm still not sure the exact cause of that error, but I'm having the code first search for the folder that the created file is supposed to go into, within it's own try/catch, and if there is an error, then I'm assuming that the drive.file scope can't access that folder, so it creates a folder and uses that newly created folder.  It's not a great solution, but it's better than a total failure.