Request entity not found about fusion-tables-drive-export HOT 5 CLOSED

Hm, the message Requested entity was not found is thrown by fire base. Might be an issue there?

from fusion-tables-drive-export.

It seems the error occurs when there is already an ft-archive folder created form a different application.

Possible solution:
include the creater (the app that created the folder) in this query:
https://github.com/google/fusion-tables-drive-export/blob/master/server-src/drive/find-file.ts#L49

from fusion-tables-drive-export.

Question remains: why do we get an error form datastore?
We should fix that as well.

from fusion-tables-drive-export.

Additional info from Russel:

One of the OAuth scopes is that the tool can write to files that this particular OAuth client has created... I had to switch cloud projects at one point (remember the app was not deploying) and so the OAuth client changed.
And the new client cannot write to the sheet ft-archive-index that the old client had created.

The solution is to rename the existing sheet from ft-archive-index to .

from fusion-tables-drive-export.

The error isn't thrown by datastore. It's the error message of a 404 error from the sheets API.

from fusion-tables-drive-export.