Skip to content
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

Error when trying to copy sheet located in multiple folders #163

Open
soelu opened this issue Jul 23, 2020 · 2 comments
Open

Error when trying to copy sheet located in multiple folders #163

soelu opened this issue Jul 23, 2020 · 2 comments

Comments

@soelu
Copy link

soelu commented Jul 23, 2020

Are you requesting a feature or reporting a bug?

Bug.

If reporting a bug, is there already an issue open for this same bug?

No.

What is the current behavior?

Error when trying to copy sheet located in multiple folders (achieved by pressing Shift-Z). The script fails with the following error:

Error: API call to drive.files.copy failed with error: File not found: . File: GDriveService. Line: 93
--
Error: We're sorry, a server error occurred. Please wait a bit and try again.. File: TriggerService. Line: 43

What is the expected behavior?

Copy the sheet as it works with a sheet that is only located in one folder.

How would you reproduce the current behavior (if this is a bug)?

  • create a "symlink" of a sheet by pressing Shift-Z and putting it in a test folder
  • copy the test folder
  • copy fail for "symlinked" file

Specify your

  • operating system: MacOS 10.15.6
  • browser: Google Chrome Version 84.0.4147.89 (Official Build) (64-bit)
@ericyd
Copy link
Owner

ericyd commented Jul 23, 2020

I appreciate you reporting this. I'm not planning on upkeeping this app but this is by far one of the most reported bugs and I've never been able to reproduce so this might be worth investigating. Thanks for the detail steps to reproduce.

@soelu
Copy link
Author

soelu commented Jul 24, 2020

I understand, that maintaining an open source tool takes a lot of time and effort, and that sometimes you just need to let go. Nonetheless, I hope this bug report tickles you enough to investigate and eventually fix this. Keeping my hopes up... 🤞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants