Publishing Google Script Addon to G Suite Marketplace SDK

4
votes

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.

error

I am pulling the project Key from File --> Project Properties: enter image description here

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?

4
google-apps-scriptgoogle-apps-marketplacegoogle-workspace
There is another post with the title of your error. Project Key is not associated with current project or the script version doesn't exist Have you seen that answer? – Alan Wells
I think that might be out-of-date - I don't see "Google Developers Console" under the Advance Google Services popup window. I think they have a dedicated menu: developers.google.com/apps-script/guides/… I do see that I have "Cloud Platform project" associated with the script which I am trying to configure G Suite Marketplace – Nathan
You could make a copy of the project, and publish the copy as an add-on. – Alan Wells
I get the same error with the copy project. – Nathan
I just published a stand alone Apps Script file to the G Suite Marketplace as unlisted, and it worked. So, it doesn't have anything to do with the Project Key. Have you checked the current version of the project from the code editor? File -> Manage versions Do you have a draft version saved in the Chrome Web Store? – Alan Wells

4 Answers

3
votes

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.

2
votes

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.

0
votes

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)'.

-1
votes

The Project key has been deprecated. Try using the Script Id instead.