brucemcpherson
Error with new Chrome V8 powered Apps Script runtime
The word 'package' seemingly wasn't a reserved word in the previous Apps Script runtime? I have disabled the new one and it works as usual, in the newer one, Stackdriver logged the following error message on encountering it as a variable name:
SyntaxError: Unexpected strict mode reserved word at [unknown function](GoaApp:43:34)
Since newer users will get auto'd to the the new runtime, this should be fixed.
Good catch
thanks - I'll take a look at it.
On Fri, 28 Feb 2020 at 07:30, Ayush Bahuguna [email protected] wrote:
The word 'package' seemingly wasn't a reserved word in the previous Apps Script runtime? I have disabled the new one and it works as usual, in the newer one, Stackdriver logged the following error message on encountering it as a variable name: SyntaxError: Unexpected strict mode reserved word at unknown function
Since newer users will get auto'd to the the new runtime, this should be fixed.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/brucemcpherson/cGoa/issues/2?email_source=notifications&email_token=AAOONBFWERWUSUSI6Z3YX4DRFC4SJA5CNFSM4K5KWJHKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IRA3QPQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOONBBK3EGBA6R4O4EBJQDRFC4SJANCNFSM4K5KWJHA .
Hi I have updated my project to use the latest version of cGoa. However I am getting the following error. SyntaxError: Unexpected strict mode reserved word (line 43, file "GoaApp", project "cGoa")
Yes - I've updated to remove the word thats now reserved in v8 . However there may be other issues to do with cross site redirection that I havent looked into yet.
On Wed, 25 Mar 2020 at 14:09, Dorian [email protected] wrote:
Hi I have updated my project to use the latest version of cGoa. However I am getting the following error. SyntaxError: Unexpected strict mode reserved word (line 43, file "GoaApp", project "cGoa")
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/brucemcpherson/cGoa/issues/2#issuecomment-603860246, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOONBHY6WOZL5SX4LJ2FIDRJIGBRANCNFSM4K5KWJHA .
Any idea if this a simple fix. if not, what other projects have a similar function. An help you can give will be appreciated. This has completely shutdown my project.
have you tried the version ive just updated?
On Wed, 25 Mar 2020 at 15:27, Dorian [email protected] wrote:
Any idea if this a simple fix. if not, what other projects have a similar function. An help you can give will be appreciated. This has completely shutdown my project.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/brucemcpherson/cGoa/issues/2#issuecomment-603905724, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOONBBFBGT2XQBLHB64LODRJIPGPANCNFSM4K5KWJHA .
OK so I updated to 31. I notice a scope is missing from my project properties section. "https://www.googleapis.com/auth/script.external_request"
Can you tell me what this means. I am getting an error that says : The Scopes must be in a valid array (line 29, file "Code") node of my files are named "Code"
It's been a couple years since wrote this code. After some more inspection actually your script is include, but It does not look like I'm using it. back then I had trying to send data to a google firebase DB. I add cGoa and GSApp to get the the Oath connection to firebase.
serverToken = new GSApp.init(key, ['https://www.googleapis.com/auth/firebase.database', 'https://www.googleapis.com/auth/userinfo.email'], clientEmail);
Sorry did not mean to waste your time. could my error: The Scopes must be in a valid array (line 29, file "Code")
be talking about these scope in the serverToken variable?
Hello, I am having the same issue "The Scopes must be in a valid array". My script has worked for years and the issue just started. I did just start getting the message about the new Chrome V8 runtime so wondering if that is related. @tourBermuda , did you ever figure out the issue?
