I'm trying to publish a Gmail Addon. I'm following guide here:
https://developers.google.com/gmail/add-ons/how-tos/publish
but each time I click save in " Apps Marketplace SDK " configuration page I get the error in the title:
"Deployment Id is not associated with current project."
That's nonsense, since the associated project has been created directly with an action triggered from https://script.google.com
I have even tried to manually create a new project, and to associate the script to the new project, operation that succeeded but the save configuration fails at the same point with the same error.
Any idea?
Are you trying to use the HEAD deployment ID? If so then that's the problem.
I had this problem, it turned out the script was not properly linked to the google cloud project. You can find instructions on doing that here
https://tanaikech.github.io/2019/07/05/linking-cloud-platform-project-to-google-apps-script-project/
Related
I'm creating forms on demand and i need to be able to set up the triggers. If i do it on the main AppsScript script that is handling the forms creation, i'll hit the 20 triggers max quota pretty soon. So i decided to add a dedicated script to every form (associating with parentID) so i won't hit the quota.
My problem is that when i try to add the triggers i'm getting permission denied since the scripts created for each form are using a default GCP project and it needs to be a standard GCP project due to OAuth.
I can add the project number manually, but that kind of defeats the idea of being able to generate google forms on demand.
I want to be able to link the script created with the standard GCP project that is already configured, but i just can't find anything on Google's documentation, i know its a long shot but i've decided to post here in hopes that someone that had the same problem managed to do so.
As requested on the comments below, the triggers that i'm using are:
onFormSubmit - get the response and send it to my endpoint in the backend server
onOpen - ensures that the editor hasn't removed anything default (this only works when an editor opens the form in edit mode)
This is the project number im referring to.
Thanks
I tried to change the version of my gmail addon before submitting it but I keep getting this error Failed to get details of the deployment ID.
Steps that I've done:
I managed to add a version to the submit form
My submission got rejected
I made some changes to the addon's code
I tried to change the addon's deployment ID to the new version but I got this error instead
This kind of error usually appears in case of a wrong Deployment ID
Common causes are e.g. spaces introduced before or after the Id.
Another possibility is that the Apps Script project is bound, while for a Google Workspace Add-on it needs to be a standalone script.
It is also possible that MarketSpace SDK does not find the script because the owner of the GCP project and the Apps Script file are not the same person.
While the following behavior would result in a different error than yours - for completion sake:
You also need to make sure that the Apps Script is tied to a Standard GCP project - namely the one to which the Add-On belongs, and that it is the only Apps Script project bound to this GCP project
I've got some Google Sheet script code that I'd like to extract into Google Sheet Addon to be published for just of our domain (not public web). Individuals on my team have been able to do this successfully in the past but after 1/25/2019 when Google removed Add-Ons from Google Chrome Store we've been having difficulties.
I am trying to follow:
https://developers.google.com/gsuite/add-ons/how-tos/publish-addons#publishing_instructions
But get the following error when trying to configure the G Suite Marketplace API:
Project Key is not associated with current project or the script version doesn't exist.
I am pulling the project Key from File --> Project Properties:
Does anyone have any idea where I am going wrong or know of good tutorial of how to publish a private Google Sheet Add-on?
I had the same problem but identified a solution as follows.
In the Google Apps Script Editor, under Resources -> Cloud Platform Project, click the ProjectName - project-id-xxxxxxxxxxxxxxxxxxx link. Then when it opens your Cloud Platform Project, in the upper left corner, your project name will be listed with a dropdown. Click the dropdown and verify that this project-id-xxxxxxxxxxxxxxxxxxx matches the link you clicked. The two numbers did not in my case and I had to refresh my screen for the correct project-id to show up in the Cloud Platform Project screen.
Don't know if this will help, but I was having the same error message and I just got it to work. I put in the value from File --> Project Properties: ->Project key (Deprecated) and still got the error. Then I changed the version to the number of my latest version and it worked.
Double check your version number - while in the script editor, click on 'File' and 'Project Properties'. I had the same problem. It turns out my error was entering the version name I had given my current version of the script (3.0), instead of the number Google had assigned to the current version of my script (3).
Once I entered '3' as the version number, I no longer got the error message "Project Key is not associated with current project or the script version doesn't exist ", and I was able to save.
I used the 'Project key (Deprecated)'.
The Project key has been deprecated. Try using the Script Id instead.
In my Google spreadsheet, when I go to "Tools->Script Editor..", I get a page saying "No Such User" Error. Any idea how to fix this?
I figure this could be a permissions issue, but not sure how to change permissions if required.
Finally i found the solution accidentally.
The issue is resolved by enabling GoogleAppsScript as part of your drive.
Open Google Drive in your web browser.
Click New > More > + Connect more Apps
and then select GoogleAppsScript.
Once i did this going back to script editor of my spreadsheet, no more gives any error.
Here is the link which contained this step:-
https://developers.google.com/drive/v2/web/quickstart/apps-script
Also there is additional problem about Invalid OAuth Client when trying to run the script. which i faced since each apps script has to be attached to a Google Cloud Project. This is accessible only to the person who originally created the file even after its in the team drive. In which case, you need to make a copy of the apps script available by going into File->Make a copy. And then in the Resources drop down , you will see Cloud Platform Project, upon clicking it you can now give the project number of the Google Cloud Platform project you created on console.cloud.google.com.
Is there a way I can reach out to someone in the Google Apps team who could help me with an outage?
I accidentally deleted the file that contained the project associated with a Sheets Addon published on the web and having 5000+ users (had a thread here: https://stackoverflow.com/questions/36704711/i-accidentally-deleted-the-google-sheet-that-contained-code-for-my-published-add)
I worked with Google Drive support to undelete the file and now I can access it, and all the code is fine.
However, since then the addon installed by so many users stopped working for everyone. It gives the users the following error:
"We're sorry, a server error occurred. Please wait a bit and try again."
I tried re-publishing a new version of the add-on, but I can't do that either, I'm getting the following error:
Any help would be appreciated.
Was able to fix this by reassigning the sheets addon code to a different Developers Console Project: Resources -> Developer Console Project... -> Change Project.
Just created a new empty project for that.
It looks like the problem was in the addon being linked to a project that for some reason got deleted when I deleted the addon code. And restoring the addon code didn't restore the association with the project.
It's still a mistery to me how a Sheets Addon depends on the Developer Console Project, but reassigning it to a different project fixed the issue. I was also able to publish an updated version of the addon, however creation of the new project triggered a manual review, so it'll take some time before new fixes will become available.