OAuth Review team can't see my Add on

[Ravi Vyas]

Hi All, 

Recently I had applied for OAuth verification, and for the same, I had to share my project with their testers (ignore the security aspects of it for now) as my app is unpublished.

Even after installing it on their end (not sure how they do it), my add-on did not show up for them. 

My best , rather only guess is I was using createMenu instead of createAddonMenu which caused the issues. 

Any insights on what the problem could be?

Also I am not sure how the rest of you got it tested, there is another thread which mentions publish the add-on first and then apply for OAuth verification, but in my case my add-on was rejected as OAuth was not verified. 

[Alan Wells]

I would think that requesting OAuth verification for the Apps Script project before publishing a new add-on,

would be the way to go.

I haven't successfully published a new add-on listing recently, so I'm not sure if things have changed.

They should have seen the custom menu even if they didn't see an add-on menu.

If they didn't see a custom menu, then probably what is happening, is that there is a fatal error when your code is parsed by JavaScript, even before anything runs.  So, you can get a JavaScript error before any code even runs.

So, what happens is, that your code to build the menu never runs because there's an error before it can even run.

That can happen during the process when your code is being evaluated by JavaScript.

That's the "classic" issue for a menu not appearing for an add-on.

Now the question is, why did the error happen?

It could be an issue with a global variable.

Or the order of your files.

Are you using V8?  See your manifest appsscript.json file.

[Andrew Apell]

Those guys can be a bit robotic with their responses sometimes. I remember having a similar issue and kept asking for clarification but they just kept sending the SAME email as a reply!

Try using "createAddonMenu"  instead and see if it works for you.

[Ravi Vyas]

Not using V8, it has issues with JDBC. 

So, it runs fine for me, and another acount I have the project shared with, when I "test as Add-on" on a sheet. But since this is a Standalone project, there is no way to persist the add-on in the menu. I am thinking of actually giving them instructions to run the "test as Add-on" process. 

If there was a JS error, would the executions screen capture the error? 

[Ravi Vyas]

Yup, that is what I have done, and am keeping my fringers crossed.

[Alan Wells]

Even before V8 there were problems with add-on menus not being created.

For years people have had issues with the code running for them,

and then when someone else runs it, it doesn't work.

But, I'm not sure it that's your problem.

In any case, I'm interested in any information that you find.

You should have error handling in your code that is logged to Stackdriver.

console.log()

Look at your executions

https://script.google.com/home/executions

for any failures.