PERMISSION_DENIED error while reading public spreadsheet with Google Sheets API

2
votes

I am using Google Sheets API v4 to read a spreadsheet content in my project. It has worked just fine for a few months, but recently I started to get a PERMISSION_DENIED error while reading some, but not all of them.

All the sheets worked properly before, but now some of them can't be read (resulting in PERMISSION_DENIED error) while the other ones still work fine. Also when I create a new sheet it does NOT work.

All the sheets are available for viewing for anyone at the web, I did not change the API key I am using, the sheet owner did not change, some sheets have not even been modified for weeks. Long story short: I did not change anything (that I am aware of) that could impact reading the sheets but yet some of sheets suddenly stopped working.

Has anything changed recently in how Google Sheets API works? Or am I missing something else?

EDIT:

A few hours passed by and some sheets that previously did not work now work and some that did work now don't. The sheets have not been modified in meantime.

May this be caused by reaching any usage limit? I don't get RESOURCE_EXHAUSTED message though. It's PERMISSION_DENIED in each case.

1
google-sheets-api
Maybe you reached your request limits? Check developers.google.com/sheets/api/limits – HaR
I don't think it's the case, because I get PERMISSION_DENIED error. When I tested how it behaves when I reach the limit (with script that did more requests than allowed) I got RESOURCE_EXHAUSTED error. Also if it was caused by reaching the limit, it should work after 100 seconds of not making any requests but it does not – turbolek
I checked in developer console and the usage was not even close to the limits – turbolek
Try these steps from forum one at a time: - Try clearing your Cache/History - Try Incognito/private window - Disable extensions/add-ons/plug-ins - Try a different browser to see if it is a browser related issue – MαπμQμαπkγVπ.0
Unfortunately none of this works. I tried various browsers, devices, google users and locations (to check if it is not IP-related issue) with no effect – turbolek

1 Answers

1
votes

Turns out it was a bug on Google side. Now everything works as intended.