-
Notifications
You must be signed in to change notification settings - Fork 937
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
Google Drive API Required after 5.11.0 #1277 #1286
Comments
Hi. Thanks for this issue :) - it is something I clearly did not anticipate when implementing #1277. Technically, our documentation says you should enable both Drive API and Sheets API. However, I can see how many people (probably myself included) would skim over it and miss out the step of enabling Drive API. #1277 means that opening a spreadsheet now requires the Drive API as it uses it to get the metadata for "last edited time" and "created time" for the spreadsheet. Please follow the paper trail in #1277 for why we changed it to be that way. If you would have attempted to access either of these properties, you would've also come across this error (no Drive API access).
Thank you very much! I can see others also having this issue. We will leave this issue open for a while so it can more easily be found. I have also added this information to the release notes |
Thanks for taking the time to reply and update the docs, and for the work maintaining this repo. |
Hi. With the new patch, you should not need Drive API access. |
After 5.11.0 (and I assume #1277), I needed to enable the Google Drive API on my project in order to open a google sheet (using any mechanism).
The error was very helpful:
But it threw me. I was making a fully unrelated code change and I couldn't figure out why I'd suddenly need to enable Google Drive API. Took me a while to track it back to this PR.
From the context, it looks like #1277 is fixing a bug, and I probably should have had Google Drive API enabled the whole time.
I'm just raising this for others / in case you think it would be helpful to document the change.
The text was updated successfully, but these errors were encountered: