New to the gmail addon (and addon in general)
I am thinking of building a gmail addon which will allow the domain admins to do a domainwide install of gmail addon so that it can appear in the "G Suite Marketplace".
However when I access the documentation "Admins of a G Suite domain can install and authorize a Docs, Sheets, or Forms add-on for all users in the domain if the add-on is published to the G Suite Marketplace using the instructions below".
Is a domain wide install of a gmail addon actually possible ? I may be missing something here.
Ref: https://developers.google.com/apps-script/add-ons/domain-wide
Yes, we can do domain wide installation by using the option "private add ons", for more information see: https://developers.google.com/gmail/add-ons/how-tos/publish
Related
how to and where to request scope "https://www.googleapis.com/auth/drive.install" in drive ui integration (in web app) for install my application in google workplace marketplace.
firstly i ceate project after this create consent screen and followed create credential (client id and secret id). i tried OAuth playground to install my aap but its not help me to find how to and where to implemnet . and i did not understand which api call or not to install my app in google workspace marketplace.
I am new to google app script. I don't know how to deploy the Google add-on. I have tried some setups for deployment but have not been able to do the deployment. so, I have some questions below.?
Can we use the google app script add-on without deploying on google marketplace? or
how to use google add-on local environment?.
or
Can we use the google add-on just by passing appscript.json? as we do in excel? In the excel add-in we just pass the manifest file and we put the dist folder on the local server so anyone can use that add-in.
Can anyone guide me about this.
I suggest you read https://developers.google.com/apps-script/add-ons/ and https://developers.google.com/workspace/marketplace
To deploy an add-on (i.e. create a version of the script that can be used by an app in the Google Workspace Marketplace) see https://developers.google.com/apps-script/concepts/deployments
To test an add-on (install it without having to publish it in the Google Workspace Marketplace)
See https://developers.google.com/apps-script/add-ons/how-tos/testing-editor-addons.
To publish an app in the Google Workspace Marketplace see https://developers.google.com/apps-script/add-ons/how-tos/publish-add-on-overview and https://developers.google.com/workspace/marketplace/how-to-publish.
Sheets and other Google Workspace products are on the cloud, so you can't copy a file somewhere to install and add-on. If you have are a Google Workspace customer you can publish a private app in the Marketplace. Then the admin can install the app for its users.
I made a script that get a Drive folder by ID and then processes a function. I first used this script on the Apps Script Editor linked to a Google Sheet file on my Drive, before migrate to an Addon : it worked like a charm. This is what the code looks like :
Line 93 :
var parentFolder = DriveApp.getFolderById('##folderId##');
Then, I published a private AddOn of that script for our domain on the Google Workspace MarketPlace. The function "DriveApp" won't work and the only log i received is :
Uncaught at functionName (Code:93)
I specify that my AddOn is published domain-wide and installed by administrator... The Google Docs says (here : https://developers.google.com/apps-script/reference/drive):
However, if an add-on using the Drive service is published for
domain-wide installation and is installed by the administrator for
some or all users in the domain, or any Apps Script that has its OAuth
client allowlisted by the domain administrator, the add-on functions
for those users even if the Drive SDK is disabled in the domain.
I prefer using DriveApp than the Advance Drive API Service. Maybe a problem with "Google Workspace Add-ons" OAuth or ...? I am stucked.
I have published tens of add-ons but now suddenly when doing everything the same way I get the error message "You must configure the G Suite Marketplace SDK to publish an add-on." when I try to publish an add-on using the "Deploy as Docs add-on" menu item. I have configured the "G Suite Marketplace SDK". BTW, the error dialog presenting the error message is linking to the console project correctly but the link replaces the current browser document, it would be better if it would open a new tab.
The message in the dialog is not an error message. They have changed the way you start the publish process. The dialog would make more sense to me if it would say:
We have changed the publish process:
Go to your console project
Enable the G Suite Marketplace SDK library
Configure the Marketplace SDK with the Config tab
Publish the add-on using the Publish tab
If you want to make a feature request to Google about the Apps Script code editor, then you'll need to use the Google Issue Tracker
Make Feature Request
Answer:
Google is currently migrating add-ons from the Chrome Web Store to the G Suite Marketplace, so now need to be published there rather than the legacy marketplace.
Further Information:
In order to publish an Apps Script project as an addon, as specified in your message, the G Suite Marketplace SDK must be configured. You can find an article detailing the migration process here.
You will need to enable the G Suite Marketplace SDK in your Google Cloud Platform (GCP) project. You can follow the information on the Getting Started page for Google Cloud.
References:
All add-ons now in the G Suite Marketplace
Publish to the G Suite Marketplace
Getting Started with Google Cloud
I wrote a Google Apps Script and successfully deployed it as a Google Sheets Add-on.
Yesterday, I found a bug, I updated the script, and I deployed a new version of the add on.
No matter what I do, I still see the old version of the add-on in Google Sheets.
I tried to:
1) Reload the Google Sheet file
2) Uninstall and install the plugin
3) Restart Chrome
4) Re-deploy the add-on
Nothing worked.
How can I force Google Sheets to update to the new version of the plugin?
UPDATE: As pointed out by Alan Wells, this is related to the following bug:
https://groups.google.com/forum/#!topic/google-apps-script-community/WTV2CGFTuHU
Workaround: publishing the plugin from the GCP Marketplace configuration screen worked for me.
Thanks,
Fabio
This issue is now fixed. Also the new GSM publishing flow, which no longer requires to publish or update a Chrome Web Store listing, is live.
To update the script of an add-on follow these instructions https://developers.google.com/gsuite/add-ons/how-tos/update-editor-addons#update_published_add-on_code.