Error in published addon

[enuchi]

Error in published addon

[lukas1994]

yeah I've seen this thread
now I'm even getting the error after doing the modification described in my initial post
using an incognito tab with only one logged in account also doesn't fix it :/

[enuchi]

Not sure if you've seen this thread: https://issuetracker.google.com/issues/150247026

Are you logged in to multiple google accounts when you're seeing this issue in your addon?

[enuchi]

How about in firefox?

[lukas1994]

this is really weird, I just added a console.log statement to the top of the file and now it works
is it usually that buggy or is there something weird going on with my setup?

[lukas1994]

one issue could also be that it takes a while to deploy the app, so that I'm seeing old versions

[lukas1994]

looks like the issue is actually just moving the functions to the top of the file
is there a way to make webpack do that automatically?

[enuchi]

Hmm. Are you running the new chrome v8 runtime or not?

Webpack is already exposing those functions, using gas-webpack-plugin. That plugin brings any functions attached to global.* to the global scope, by first declaring them as functions at the top of the script and then defining the function body below. See line 1 in the included example app. If it only works when you define the full onOpen function at the top then maybe there are other permissions errors that are throwing in the bundled webpack script. I'm not sure.

Are you running the new chrome v8 runtime? There might be some discrepancies between the new v8 runtime and functions in the global scope but I haven't encountered these.

And does the app work for you if you run the demo app?

[lukas1994]

looked like it was a clasp issue,
just created this: google/clasp#761
for now, the work-around is to create the version in the UI

[lukas1994]

BTW I'm using v8 if that helps.

[pragi-balasubramanian-alation]

@lukas1994

Help me: google/clasp#761 (comment)