Can we do something about the issue #69270374 - "Authorization is required to perform that action" ?

[Faustino Rodriguez]

It's my first post, so I wanted to touch an important pain point on my side (literally)

We spent a few hours a week supporting users that are struggling with this issue

https://issuetracker.google.com/issues/69270374

Can somebody around here gets Google's attention on this issue?

The issue started on Nov.13, 2017 and it is potentially affecting every add-on out there

It is still with status New and Unassigned

Sorry for ruining the forum inauguration party ;)

[Romain Vialard]

I agree with you, surprising that it still isn't fixed.

The workaround I implemented in YAMM and described in the following blog post does work well and avoid spending "a few hours a week supporting users that are struggling with this issue" so I would recommend implementing that rather than waiting for an official fix.

[Faustino Rodriguez]

I did something like that long ago (thanks again for your support), but still it's not 100% effective

- sometimes, the user just log-out from the default account without removing it from the browser, and the issue persists

- in other cases, they have no idea what I am talking about, and just give up on using the add-on

[Alan Wells]

I display an error message with red background, and put my email at the very top.  Even if they don't read the error message, they can see that something is very wrong, and see my email.  In some situations there are space constraints, so a full explanation of what the problem is, and what to do about it may get truncated.  Do you collect the users email when the add-on is installed?  And do you send them error messages?

[Darren D'Mello]

Yes still the issue persists inspite of workaround. Thanks to Romain Vialard for this hack.

--
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.
Visit this group at https://groups.google.com/group/google-apps-script-community.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/55c8a86f-f822-476c-99d3-abf1d7682a89%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Faustino Rodriguez]

Yes, we send the users follow up emails for some errors, including this one, with some details and suggestions on how to avoid them

This particular error is the top-most-frequent error we get in the Log

[Eric Koleda]

I've posted an update on the issue tracker and I'll put it back on the engineering team's radar. No promises it will result in a fix anytime soon though.

- Eric

--

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.
Visit this group at https://groups.google.com/group/google-apps-script-community.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/6ca40130-f32e-4473-a3b5-26250e90ed3e%40googlegroups.com.

[Faustino Rodriguez]

Thanks a lot Eric, for the update and the explanations.

On Monday, March 18, 2019 at 10:34:15 AM UTC-4, Eric Koleda wrote:

I've posted an update on the issue tracker and I'll put it back on the engineering team's radar. No promises it will result in a fix anytime soon though.

- Eric

On Fri, Mar 15, 2019 at 12:02 PM Faustino Rodriguez <fau...@thexs.ca> wrote:

Yes, we send the users follow up emails for some errors, including this one, with some details and suggestions on how to avoid them

This particular error is the top-most-frequent error we get in the Log

On Friday, March 15, 2019 at 11:54:57 AM UTC-4, Alan Wells wrote:

I display an error message with red background, and put my email at the very top.  Even if they don't read the error message, they can see that something is very wrong, and see my email.  In some situations there are space constraints, so a full explanation of what the problem is, and what to do about it may get truncated.  Do you collect the users email when the add-on is installed?  And do you send them error messages?

--
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-community+unsub...@googlegroups.com.

[Darren D'Mello]

Eric please, any update on this. This error is really frustrating.

The workarounds don't work most if the time.

[Eric Koleda]

Hi Darren,

Unfortunately there aren't any updates. I'm continuing to stress the importance of this to the engineering team, but I don't know if or when they will take action.

- Eric

On Thu, Mar 28, 2019 at 11:43 PM Darren D'Mello <miscellan...@gmail.com> wrote:

Eric please, any update on this. This error is really frustrating.

The workarounds don't work most if the time.

--
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.
Visit this group at https://groups.google.com/group/google-apps-script-community.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/a6672935-88cb-46ec-9552-afbfdc93e9f8%40googlegroups.com.

[Steve Webster]

Thanks for mentioning this. I wonder how much money has been lost by developers or companies due to this issue.

Kind Regards,

Steve Webster

SW gApps, President 

Google Product Expert in: Google Apps Script, Drive, and Docs 

Google Vendor (2012-2013) || Google Apps Developer Blog Guest Blogger 

Add-ons: Text gBlaster and Remove Blank Rows

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/CAC5MyAP%3DG4_zfrvw%2BuhmX%2BwAwt3BRVAhvQu5q4R_RVVpJORv3Q%40mail.gmail.com.

[Darren D'Mello]

Perfect Steve, I am too frustrated. A Search Giant couldn't overcome such a bug...

Thanks to Fausto, for posting this to be the first post. Its a pain.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/CA%2BV5gQ71s%2B1yhn0QTfmjhbe1mqHXOz_fMzcyrhJ2yjNSBLtPtw%40mail.gmail.com.

[Alan Wells]

Do you know the specific details of when the "work around" doesn't work?  According to the post by Romain Vialard, the issue is only affecting multiple accounts in the same domain.  Do you know what account logged in first?  Do you know if the multiple accounts are in the same domain?  Do you know whether the default account is the same as the account that authorized the add-on?

[Darren D'Mello]

This bug is weird. I have seen this happens when 2 accounts (same or different domain sometimes) are signed in.

The exact behavior is unpredictable and difficult to mimic for debugging.

--
You received this message because you are subscribed to a topic in the Google Groups "Google Apps Script Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-apps-script-community/qdKd4caD_hY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-apps-script-c...@googlegroups.com.

Visit this group at https://groups.google.com/group/google-apps-script-community.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/2d6d50bd-88b4-4675-bc99-c54d0d540c87%40googlegroups.com.

[Faustino Rodriguez]

Any hope on fixing this issue before its 2nd anniversary on this Nov.13

@Eric and any @Googlers around: any updates?

...thanks

On Friday, March 29, 2019 at 8:39:44 PM UTC-4, miscellaneousmailer wrote:

This bug is weird. I have seen this happens when 2 accounts (same or different domain sometimes) are signed in.

The exact behavior is unpredictable and difficult to mimic for debugging.

On Sat, Mar 30, 2019, 12:00 AM Alan Wells <aj.a...@gmail.com wrote:

Do you know the specific details of when the "work around" doesn't work?  According to the post by Romain Vialard, the issue is only affecting multiple accounts in the same domain.  Do you know what account logged in first?  Do you know if the multiple accounts are in the same domain?  Do you know whether the default account is the same as the account that authorized the add-on?

On Thursday, March 28, 2019 at 11:43:41 PM UTC-4, Darren D'Mello wrote:

Eric please, any update on this. This error is really frustrating.

The workarounds don't work most if the time.

--