Just wanted to log findings just in case someone else runs into the issue. This appeared to be a Google Access Token Expiration issue. Please see Aleksiโs notes below:
How Google-based signin works for a โthird-partyโ app like AppSheet. And this princple goes to all providers, not just with Google.
#1 - The user goes to AppSheet and says โsign in via Googleโ
#2 - AppSheet redirects the user to a page hosted by Google
#3 - Google asks the user โ hey do you trust AppSheet because it is going to access your Drive and Sheets. The user says โ yes, I trust AppSheet.
#4 - Google returns the user to AppSheet and gives AppSheet a token that AppSheet can use in making calls to Google to read and write data. This is called an โaccess tokenโ and tells Google we are doing it on behalf of this specific user. That is how we can read/write your files.
#5 - But Google wants to make sure you can change your mind at any time. Soโฆ
#6 - It makes the access token valid for only one hour.
#7 - It also gives AppSheet a โrefresh tokenโ and AppSheet needs to send this to Google every time the access token expires and ask โ please give me a new access token.
#8 - If you (or Google) has decided to stop giving AppSheet permission, this refresh request fails. And after that, AppSheet can no longer read or write your Google data. When does this refresh request fail?
There are few reasons:
#9 - If you explicitly decide to deny AppSheet permission, you can go to accounts.google.com and disable access.
#10 - All providers are expiring the token time to time
Development accounts should logout of all applications associated with the data source to reset the token and/or contact support@appsheet.com if the issue doesnโt resolve.
LinkedIn
Twitter
