Issues with webapps / V8?

[Pablo Felip]

Hi, all.

This morning I noticed that one of my webapps (a simple web form that stores data in a Spreadsheet with file upload to Drive) had stopped working unexpectedly, displaying some storage error and details about an unauthenticated access (?) inside the browser's window. The code in the script editor was unaccesible (spreadsheet bound script) for a while (Forbidden - 403). Other instances of this same script / webapp kept working without a hitch.

After repeated attempts, I could finally open the code editor in the affected spreadsheet, but the aforementioned error when accessing the webapp was still manifesting. Somehow, the V8 engine had been activated on its own. Webapp has not been functional again until going back to Rhino.

I think that in its current state, V8 auto enabling could pose serious problems in many already deployed scripts. Maybe this has been just a spurious error affecting this particular Spreadsheet, but just in case, I'd like to ask if you have experienced a similar circumstance recently.

Thanks in advance.

PS: Partially related to this? (I was quite sure to be logged in with just one account, though)

[Mani Doraisamy]

Yes. I had a similar problem while using People API. 

Looks like V8 engine doesn't seem to use addon user's credentials which calling the Google APIs. I had to revert back to Rhino engine to get it working again.

regards,

mani

On Fri, Mar 6, 2020 at 11:25 AM Pablo Felip <pfe...@gmail.com> wrote:

Hi, all.

This morning I noticed that one of my webapps (a simple web form that stores data in a Spreadsheet with file upload to Drive) had stopped working unexpectedly, displaying some storage error and details about an unauthenticated access (?) inside the browser's windows. The code in the script editor was unaccesible (spreadsheet bound script) for a while (Forbidden - 403). Other instances of this same script / webapp kept working without a hitch.

After repeated attempts I could finally open the code editor in the affected spreadsheet , but the aforementioned error when accessing the webapp was still manifesting. Somehow, the V8 engine had been activated on its own. Webapp has not been functional again until going back to Rhino.

I think that in its current state, V8 auto enabling could pose serious problems in many already deployed scripts. Maybe this has been just a spurious error affecting this particular Spreadsheet, but just in case, I'd like to ask if you have experienced a similar circumstance recently.

Thanks in advance.

--
You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/c872e752-e8d2-49f3-ae2d-f4a50a72f45b%40googlegroups.com.