Status Update
Comments
ga...@google.com <ga...@google.com> #2
In order to try and replicate this in my test environment, please can you provide the following information:
1) Is the script with the failing onInstall(e) trigger bound to a file?
2) What are the OAuth consent screen settings you have set up for this project?
3) Which extension addon-ons are enabled for this project in the G Suite Marketplace SDK configuration?
4) Has this add-on been published on the G Suite Marketplace publically, or just for you domain?
Many thanks!
su...@formapprovals.com <su...@formapprovals.com> #3
Please see responses below:
1) Is the script with the failing onInstall(e) trigger bound to a file? The script is container bound to a Google Form. The script is published as a public add-on in the G Suite Marketplace for user and domain wide install.
2) What are the OAuth consent screen settings you have set up for this project? The application type is Public. The scopes used and approved are script.send_mail, script.external_request, gmail.send, spreadsheets, script.scriptapp, script.storage, forms, openid, userinfo.profile, userinfo.email. Let me know if there is anything else you need here.
3) Which extension add-ons are enabled for this project in the G Suite Marketplace SDK configuration? This is a Forms editor add-on extension only.
4) Has this add-on been published on the G Suite Marketplace publicly, or just for you domain? Publicly.
Let me know if there is any other information required to assist.
Thank you,
Robert
ga...@google.com <ga...@google.com> #4
Thank you for your response to my previous questions. I have been able to reproduce this behaviour in my test environment and have made an internal report about this. If you'd like to keep updated on this issue, please give this page a star in the top left.
Many thanks!
ho...@gmail.com <ho...@gmail.com> #5
op...@gmail.com <op...@gmail.com> #6
It's 10 days since the Google Team member confirmed the issue. Any estimates on fixing? Thanks!
aa...@gmail.com <aa...@gmail.com> #7
fr...@gmail.com <fr...@gmail.com> #8
Installing the add-on from Google Doc do not trigger onInstall().
Full report:
an...@quicklution.com <an...@quicklution.com> #10
The onInstall(e) function is not being triggered. It happens 100% of the times in my case.
ma...@gmail.com <ma...@gmail.com> #11
It has cost me one bad evaluation so far. Really annoying bug
i hope you'll be able to remove the evaluation too :(
[Deleted User] <[Deleted User]> #12
at...@google.com <at...@google.com> #13
We are investigating and it seems this happens when the Script ID is provided instead of the Project key.
Can you try the following workaround, please? In the GSM SDK check whether the Script ID of the editor add-on starts with 1. If it does, open the corresponding script in Apps Script, and click on File -> Project properties. Copy the Project key (starts with M) and paste it in the GSM SDK. Save the change and try installing the add-on again.
an...@quicklution.com <an...@quicklution.com> #14
HOWEVER, when installing the add-on (through an Editor) for the 1st time, the Wizard doesn't go through all the steps and therefore users think that it installed when it actually did not. Therefore they got to find it under Add-ons and don't find ANYTHING (this time). They would have to go to Get Add-ons again and attempt to install it for the 2nd time. Then it all comes up fine.
Therefore this workaround is WORSE than the original problem. I reverted back to using the Script ID.
ho...@gmail.com <ho...@gmail.com> #15
The project key is deprecated based on the documentation
bb...@gmail.com <bb...@gmail.com> #16
But I have a fear that when the bug is repaired, we will again have to return the Script ID instead of the Project key in the GSM SDK Configuration section. I hope they will notify us of the need to do this.
at...@google.com <at...@google.com> #17
Thanks for the confirmations. We are working on a fix so that onInstall is called when either the Script ID or the Project key is provided.
ma...@gmail.com <ma...@gmail.com> #18
My activity rate for new users has dropped significantly because of this bug.
I confirm that the workaround is worst than the issue because it breaks the installation flow.
at...@google.com <at...@google.com> #19
The fix has been submitted, now it has to be rolled out as part of the editors, which have a slow rollout process. Note that the workaround does not affect the installation flow.
ho...@gmail.com <ho...@gmail.com> #20
"it has to be rolled out as part of the editors" => Can you please explain what does this mean?
at...@google.com <at...@google.com> #21
It means that the code has been fixed but it's still not in production, so you won't see the fix yet.
gn...@gmail.com <gn...@gmail.com> #22
Eagerly waiting for the fix to roll out quickly. Wondering why the status of this issue still shows as "New" rather than "Under fix review" or something else.
gn...@gmail.com <gn...@gmail.com> #23
Even the above-mentioned workaround using deprecated project key won't fix, it also added a worst install experience saying the "This app is not verified" check attachment
at...@google.com <at...@google.com> #24
It seems that you haven't verified your OAuth client, which is unrelated to this issue. Please take a look at
gn...@gmail.com <gn...@gmail.com> #25
OAuth verification status for our Add-ons is published. Since we hit with this issue, we tried the workaround as mentioned above, but that didn't work. Anyway, we are waiting for this fix to be released, If you could mention ETA it will help us.
at...@google.com <at...@google.com> #26
The publish status of your add-on is independent of the OAuth verification. If you get the "This app is not verified" warning now, you'll still get it after this issue is fixed.
For more information about OAuth verification check
an...@quicklution.com <an...@quicklution.com> #27
gn...@gmail.com <gn...@gmail.com> #28
Its almost been 4 months, this bug is a serious production issue, our launch highly depends on this fix, the bug status not even changed, it's a serious concern with developers & business. Google support is barely helpless
ma...@google.com <ma...@google.com> #29
mi...@gmail.com <mi...@gmail.com> #30
Please let us know ASAP, We are losing lot of customers.
mi...@gmail.com <mi...@gmail.com> #31
Could you please send us the status ? When would you be able to solve this?
cr...@gmail.com <cr...@gmail.com> #32
ma...@gmail.com <ma...@gmail.com> #33
mi...@gmail.com <mi...@gmail.com> #34
We are very unfortunate to have this error. It severely impacts our business. As it was not at all taken serious.
Please let us know the status of this issue.
.
ma...@google.com <ma...@google.com> #35
We understand the frustration around this bug, and appreciate your patience. This issue should be fixed by the end of the week. We will post an update here as soon as it is done.
Thank you.
gn...@gmail.com <gn...@gmail.com> #36
Thanks, hope this issue also will be fixed
al...@nativeplatform.co.uk <al...@nativeplatform.co.uk> #37
Our user engagement is impacted badly, we received a huge amount of bad reviews due to bugs on Google side which we can't solve ourselves.
[Deleted User] <[Deleted User]> #38
ma...@google.com <ma...@google.com> #39
sa...@gmail.com <sa...@gmail.com> #40
mi...@googlemail.com <mi...@googlemail.com> #41
Now after installing the Sheets AddOn I get a screen: "Updated add-on"
(see attachment) and than "This app isn't verified".
It looks like a new scope is required by my Add-on: "See, edit, create and delete your spreadsheets in Google Drive".
But neither in my appsscript.json nor in the Marketplace SDK Configuration my scopes have been changed.
That means the "fix" for this error did implicitly add this scope to my AddOn.
URL:
Am Do., 30. Apr. 2020 um 23:30 Uhr schrieb <buganizer-system@google.com>:
[Deleted User] <[Deleted User]> #42
Can you give us different script id's that don't start with 1? Maybe that would have been a smarter fix? Meanwhile our Add-ons are getting roasted in the marketplace and you don't seem to give a crap.WAKE UP!
mi...@gmail.com <mi...@gmail.com> #43
Very bad to hear this... We are all blasted here because of the Google bugs
those are prevalent...
On Sat, May 2, 2020, 2:54 AM <buganizer-system@google.com> wrote:
ig...@nativeplatform.co.uk <ig...@nativeplatform.co.uk> #44
[Deleted User] <[Deleted User]> #45
ig...@nativeplatform.co.uk <ig...@nativeplatform.co.uk> #46
ma...@google.com <ma...@google.com> #47
Can I get the URL's for adversely effected add-on's, so we can test them?
Thanks.
ig...@nativeplatform.co.uk <ig...@nativeplatform.co.uk> #50
al...@nativeplatform.co.uk <al...@nativeplatform.co.uk> #53
Agree with st...@gmail.com. -> seems like you only leave is with the option to redirect customers here.
ma...@google.com <ma...@google.com> #54
Thank you.
mi...@googlemail.com <mi...@googlemail.com> #55
attached
1: An additional scope was added to my Add-on which is not from my code or
settings.
2: The Add-on menu only has the Help entry after installation. Reload
populates the menu as it is filled from onOpen(e).
Am Mo., 4. Mai 2020 um 18:38 Uhr schrieb <buganizer-system@google.com>:
pa...@gmail.com <pa...@gmail.com> #56
pa...@gmail.com <pa...@gmail.com> #57
sa...@gmail.com <sa...@gmail.com> #58
In a prior post you mentioned that the fix is deployed and would be 100%
soon. Can you please let me know the status of the fix?
As you can see there is only a help menu item showing up after install and
the rest of the menu shows up only after refreshing the sheet.
On Mon, 4 May 2020 at 22:08, <buganizer-system@google.com> wrote:
mi...@gmail.com <mi...@gmail.com> #59
ma...@google.com <ma...@google.com> #60
Thanks.
ig...@nativeplatform.co.uk <ig...@nativeplatform.co.uk> #61
mi...@googlemail.com <mi...@googlemail.com> #62
This only happens when installing from inside an open sheet.
It does not ask for that additional permission when installing via the URL
Or should I file a new bug report?
Thank you.
ma...@google.com <ma...@google.com> #63
ma...@google.com <ma...@google.com> #64
[Deleted User] <[Deleted User]> #65
mi...@gmail.com <mi...@gmail.com> #66
Also there is no flag option to mark the review as inappropriate.
Why is that so? Please advise
On Thu, May 7, 2020, 12:04 AM <buganizer-system@google.com> wrote:
fr...@gmail.com <fr...@gmail.com> #67
Best,
Le mar. 5 mai 2020 à 21:10, <buganizer-system@google.com> a écrit :
op...@gmail.com <op...@gmail.com> #68
I didn't get any messages about the issue from customers yesterday but the number of new daily users is low in my project.
mi...@googlemail.com <mi...@googlemail.com> #69
op...@gmail.com <op...@gmail.com> #70
al...@dolphiq.nl <al...@dolphiq.nl> #71
mi...@googlemail.com <mi...@googlemail.com> #72
The OAuth I mentioned could be a side effect of the fix they did, that's why I added it in my previous comments.
ma...@google.com <ma...@google.com> #73
The fix has been rolled out. For all developers who are using the onInstall() function, please let us know if your menu's are still not loading on new installations. Please include the URL for your Add-on in your comment.
Thanks.
mi...@googlemail.com <mi...@googlemail.com> #74
sorry, still not creating the menu.
Thanks.
Am Do., 7. Mai 2020 um 20:42 Uhr schrieb <buganizer-system@google.com>:
ig...@nativeplatform.co.uk <ig...@nativeplatform.co.uk> #75
Just realised, why our original
aj...@gmail.com <aj...@gmail.com> #76
op...@gmail.com <op...@gmail.com> #77
Also, onInstall() is failing not for every customer but for some of them. I
don't know why.
On Thu, May 7, 2020 at 10:49 PM <buganizer-system@google.com> wrote:
mi...@googlemail.com <mi...@googlemail.com> #78
the onInstall(e) function is not executed. Only when installing from inside the google doc/sheet/form/...
the onInstall(e) function is called. Problem here is that case.
When onOpen(e) runs just fine, onInstall(e) should as well (at least when onInstall(e) only calls onOpen(e)).
gn...@gmail.com <gn...@gmail.com> #79
The fix is not working could see only the Help menu. Here is the app link
Btw, the post-install behavior changed, a dialog asking permission for script to run (check attachment)
mi...@googlemail.com <mi...@googlemail.com> #80
I have filed a new issue regarding that:
I beforehand contacted the OAuth team and they responded that I should create a new ticket, it is not an OAuth issue.
ma...@gmail.com <ma...@gmail.com> #81
Please Google, don't wait a few months to solve it this time. The scary message for unverified add-ons is really bad to establish trust with the users
ma...@gmail.com <ma...@gmail.com> #82
- If the add-on is installed from an external window of the G Suite Marketplace, the installation process is as usual, but the Add-ons menu is not refreshed in already-opened spreadsheets unless I reload the spreadsheet.
- if the add-on is installed from the Get add-on modal in Google Sheets, the installation process is as usual until it shows the dialog asking permission for script to run.
Worse, if I click "Continue" it says my app hasn't been verified.
If I click Advanced, and process to consent anyway, the consent screen appears with an additional scope "See, edit, create, and delete your spreadsheets in Google Drive".
I used to have this scope defined for my add-on, but it's not the case anymore. I've check the OAuth 2.0 scopes in G Suite configuration, the admin OAuth consent screen page and my manifest file. In no part this scope appears.
ma...@gmail.com <ma...@gmail.com> #83
It adds:
"As part of our efforts to maintain a safe application ecosystem, Google’s automatic protections limit the number of users of apps that are not verified to use sensitive or restricted scopes."
But my add-ons are all verified and with verification status set to "published"
ma...@google.com <ma...@google.com> #84
Can you please create a separate bug for your particular issue, and we will address it over there. I have also added you to another bug.
Thanks.
at...@google.com <at...@google.com> #85
ma...@gmail.com <ma...@gmail.com> #86
al...@dolphiq.nl <al...@dolphiq.nl> #87
gp...@socialfrontier.com <gp...@socialfrontier.com> #88
ma...@google.com <ma...@google.com> #89
ma...@google.com <ma...@google.com> #91
I have added you to another bug regarding verification issue. I will follow up with you on it there.
Thanks
gp...@socialfrontier.com <gp...@socialfrontier.com> #92
gn...@gmail.com <gn...@gmail.com> #93
Please let me know which issue id you are going to follow?
gn...@gmail.com <gn...@gmail.com> #95
Thank you for sharing the issue link.
ma...@google.com <ma...@google.com> #96
[Deleted User] <[Deleted User]> #97
I'm not seeing the additional oauth screen, but I am seeing a case where onInstall() is not run. An error message shows up in the browser console saying "We're sorry, a server error occurred while reading from storage. Error code PERMISSION_DENIED"
Should that be tracked as a separate issue or should I add more repro steps here
Thanks!
e....@gmail.com <e....@gmail.com> #98
jo...@johannesklampfl.com <jo...@johannesklampfl.com> #99
mi...@googlemail.com <mi...@googlemail.com> #100
gn...@gmail.com <gn...@gmail.com> #101
Switching back to legacy Rhino runtime all mentioned issues disappear, we are going to test with multiple users...will update soon
ma...@google.com <ma...@google.com> #102
aj...@gmail.com <aj...@gmail.com> #103
It's possible to have an error parsing the code before any of your code even runs. And if that happens, I don't think that try/catch will catch an error. I not sure if Stackdriver "console.error" will catch a parse error when JavaScript is being compiled. Plus, in development, your code can be running just fine, with either Rhino or V8, but when the code gets uploaded to the GSuite Marketplace, then suddenly it fails.
[Deleted User] <[Deleted User]> #104
Repro steps:
I was previously running with this in my appsscript.json
{
"timeZone": "America/Los_Angeles",
"dependencies": {
},
"exceptionLogging": "STACKDRIVER",
"runtimeVersion": "V8",
"oauthScopes": [
"https://www.googleapis.com/auth/script.container.ui",
"https://www.googleapis.com/auth/spreadsheets.currentonly"
]
}
I had reduced my Code.ts down to
function onInstall(e ) {
console.log("onInstall")
onOpen(e)
}
function onOpen(e) {
console.log('onOpen')
}
and wasn't seeing any logs as a privately published sheets add on installed via G Suite Marketplace.
Workaround I updated my appsscript.json runtimeVersion to
"runtimeVersion": "DEPRECATED_ES5",
Was able to see onInstall
and onOpen
messaging in stackdriver, after uninstalling, then installing again from G Suite Marketplace.
al...@dolphiq.nl <al...@dolphiq.nl> #105
Hopefully we will be able to run in in Runtime V8.
ma...@google.com <ma...@google.com> #106
For all developers who are using the onInstall() function, please let us know if your menu's are still not loading for new installations. The add-on must be installed from the editor menu (Add-on's -> Get Add-on's) and not from GSuite Marketplace. If the add-on menu is not loading please include the URL for your Add-on in your comment.
Please note that the v8 verification/scope bug is a separate issue and being dealt with here:
Refer to this issue if, upon installation from the editor, the add-on runs into 'script permission' or 'unverified app' warnings.
mi...@googlemail.com <mi...@googlemail.com> #107
for my add-on
- the onInstall() function is not executed when I have configured V8
- the onInstall() function is executed when I have configured Rhino
Currently my add-on is publish using V8 - maybe this is relevant for your investigations?
ma...@google.com <ma...@google.com> #108
ja...@checksheet.app <ja...@checksheet.app> #109
The add-on must be installed from the editor menu (Add-on's -> Get Add-on's) and not from GSuite Marketplace.
To clarify, onInstall()
won't be called when the user installs from the marketplace outside of a spreadsheet?
If that's the case I feel like this should be noted as a caveat in the docs:
mi...@googlemail.com <mi...@googlemail.com> #110
my add-on has both issues.
I' aware that the unauthorized scope request is an issue with v8 and I'm aware that is a separate issue.
Nevertheless the onInstall() not executed is a v8 issue as well!
Thanks!
jo...@johannesklampfl.com <jo...@johannesklampfl.com> #112
It seems to stop working!
14. May: 49 FINISH_INSTALL events in Google Analytics
15. May: 58 FINISH_INSTALL events in Google Analytics
14. May: 57 onInstall() function calls in Google Cloud Platform - Logging
15. May: 24 onInstall() function calls in Google Cloud Platform - Logging
I am aware that there will always be differences between different tools.
Anyway, the difference on 14. May is acceptable: 49 VS. 57
Whereas the difference on 15. May seems to be too big: 58 VS. 24
In addition users start to complain again.
Please fix this bug asap. Thank you in advance.
ja...@checksheet.app <ja...@checksheet.app> #113
@ma...@google.com
I think those docs have the same problem as the ones I posted, they don't make it clear that onInstall()
won't get called if an add-on is installed from
Ideally onInstall()
would get called any time an install happens, as its name implies.
ho...@gmail.com <ho...@gmail.com> #114
The thing we need here is that onInstall
must work even when the user installed the add-on from
So if at the moment, it still does not work from
ma...@google.com <ma...@google.com> #115
mi...@googlemail.com <mi...@googlemail.com> #118
I switched back to Rhino for my add-on.
Google team: What are the plans to cutoff Rhino? Any timeframe?
When switching from Rhino to V8 in future: How we can test that everything works without affecting (new) users?
We would need a kind of "publish for specific google accounts". Anything planned in that direction?
mi...@googlemail.com <mi...@googlemail.com> #119
In the onEdit trigger I have to show ui.alert() when user makes wrong input
but in Rhino I get a javascript error that the required permission is missing.
In V8 the alert is displayed.
mi...@googlemail.com <mi...@googlemail.com> #120
That is an error in V8 that simple onEdit() trigger allow alert() or msgBox().
Behaviour according to documentation should be like in Rhino to throw an error.
jo...@johannesklampfl.com <jo...@johannesklampfl.com> #121
2) When I install a new add-on the menu of the newly installed add-on does not show up (maybe the add-on "Form Notifications" is using the V8 runtime) --> OLD BUG
3) In addition the menu of all previously insalled add-ons do not show up --> NEW BUG #1
4) When I reload my form, I can again see the menu of all installed add-ons --> works
5) When I uninstall an add-on, the menu of all other add-ons are hidden again --> NEW BUG #2
Please see video attached.
jo...@johannesklampfl.com <jo...@johannesklampfl.com> #122
I found out that it is even enough to open the add-ons window, you do not need to install / uninstall a new add-on.
Only click the "three dots" and click "Add-ons", then the menu of all add-ons will be hidden.
ma...@gmail.com <ma...@gmail.com> #123
May I remind you that this issue has been created at the end of 2019! It's been 6 months!!
ma...@google.com <ma...@google.com> #124
Please report the issue here and we will follow up on it: Public Trackers > G Suite Developers > Editor Add-ons
ma...@google.com <ma...@google.com> #125
ja...@checksheet.app <ja...@checksheet.app> #127
I don't think the original issue described here is fixed..
If you install an add-on from the marketplace, outside of a spreadsheet, then the onInstall()
function is not called.
I can re-produce this with my own add-on:
Description
When a users installs an add-on, by opening up their Google Form, selecting "More", then "Add-ons", then locating and installing the add-on the onInstall(e) method is triggered. However, when a user installs an add-on by locating and installing the add-on directly from the G Suite Marketplace, the onInstall(e) method doesn't appear to be triggered (and no log / error is being shown in StackDriver).
Developers use the onInstall method to do various things (e.g send the user a welcome / instructional email). With the recent move to the G Suite Marketplace, these instructional emails are even more important as many users install add-ons via the G Suite Marketplace now but never actually use them. When installing from the G Suite Marketplace, users tend to dismiss the popup instruction provided by Google to access the add-on via their form.
A small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup, without external dependencies.
function onInstall(e) {
onOpen(e); // only relevant when the user installs from their form directly
console.log("Test log to see if onInstall is run");
}