My app is finally published in the G Suite Marketplace. However, I need to update the banner image as it's blurry and the [Publish] button is always greyed out. What is missing from this screenshot?
Go into the OAuth Consent Screen, under "APIs and Services" and check that everything is filled in there too. The scopes for example don't always get automatically completed.
I realize this is a very flimsy answer but after playing with the form, ensuring that I filled in every field, the publish button finally became available.
My guess is that a field labelled as optional is required.
The instructions to update an Editor add-on where last updated on 2020-01-21.
Key things that you should check
The scopes in the add-on project, OAuth consent and G Suite Marketplace Config page match.
Al the required fields on the G Suite Marketplace Config page are filled (Google made some fields as required that weren't before)
Also you could try using Chrome in incognito mode with all the Chrome extensions disabled.
Related
I have published an external Google Spreadsheets addon, and everything worked so far. Since a couple of days, within the "Google Cloud Platform > APIs & Services > G Suite Marketplace SDK > Configuration panel" the input field for "Sheets add-on script version" is empty and an error message "At least one extension must be enabled and selected extensions must be configured" is displayed.
I have already tried the following steps:
Insert the current published script version number and click "Save changes"
Insert a new script version number and click number and click "Save changes"
The response is the following:
Error Sorry, there’s a problem. If you entered information, check it
and try again. Otherwise, the problem might clear up on its own, so
check back later.
Tracking Number: 7178656512110690803
Send feedback
The problem did not clear up so far and also the Google Support team did not reply to my feedback/message so far.
Due to this behaviour I am not able to publish new versions.
It is a new bug. Please star the issue on Issue Tracker for updates.
I work in the G Suite Marketplace. This issue has been fixed and it will roll out to production between today and tomorrow.
I created a google sheets addon that pulls some information from gmail and displays it in a specific format on a worksheet. This addon is to be used only by my account so I've set it as unlisted in the webstore. I've published this addon to google and paid my $5. It looks like everything got accepted just fine and when I see the definition of the addon on the store it says: Published / GAM: Pending under Status.
Initially, when I clicked on the Addon's Name in the Developer Dashboard I was able to see what the Addon would look like in the store and there was a link to install the addon for free. When I would click this link I would get taken to an empty google sheet and then after a few seconds I would get a pop-up that would say "Add-on not found. Try again, or check back later." I did as suggested and tried several times later with no luck. Then after a while when I now visit the chrome developer dashboard and I click the addon's Name I get taken to the G-Suite Market place page not the addon's page. I tried replushing the addon but still got the same results.
Does it take hours for google to process unlisted addons? Is there something that I a missing? I read something about google store migrating to G suite market place, is this part of the problem?
When the Add-ons menu is choosen in a Google spreadsheet, and the "Get add-ons" menu item is clicked, the GSuite Marketplace now opens by default.
The changes that you have experienced are because of the migration of add-ons from the Chrome Web Store to the GSuite Marketplace.
It is still possible to navigate to your listing in the Chrome Web Store, but you can't do that through the old Chrome Web Store developer dashboard. You need to go to the new Developer Dashboard. The problem is, that even though you can see the unlisted add-on listing in the Chrome Web Store, it can't be installed.
New Chrome Web Store Developer Dashboard
In the status column you will see a Published-Unlisted status for your add-on.
If you don't use the new Chrome Web Store developer dashboard, then you may not be able to find your listing at all for add-on published as unlisted.
I'm bumping into a weird problem in Google Apps Script, working on a Slides add-on.
When I run the add-on in an incognito window with just one user logged in (call it User B), everything works fine.
When I run the add-on with multiple users logged in (call it Users A and B in the same Chrome tab), it seems like Apps Script gets confused around the authorization. When I try to use the add-on as User B (as evidenced by the profile showing up in the upper right corner), all functionality of the add-on fails, I'm guessing because it lacks authorization. Note that the add-on has remain installed on User B's account this whole time, and it still works in the incognito window with just User B logged in.
Any tips on this? Is there a way to "force" the add-on to use the authorization of User B in the multi-logged-in case?
Having multiple log-ins active in the same browser is known to cause issues with Google Authorization.
The default account (typically the account that was first logged into) takes precedence over any other accounts. Google has yet to fully resolve this. Current work-around is to recommend to your users to log out of all other accounts.
I had the same problem and got it solved by changing the link as follows:
https://script.google.com/a/{any_character}/macros/s/{deployment_id}/exec
Note that my app was set public so anyone can access it.
Use this url to test instead:
https://script.google.com/a/{domain name}/macros/s/{token}/exec
The help text on Google Play Console is confusing. While we can set up a release to rollout for an internal test, it says* that a rollout to any track automatically sets the status to Published, and makes it visible on Google Play.
It must be possible to provision the test release to the internal testers before it is rolled out and visible on Google Play, right? How?
See "New Apps" at https://support.google.com/googleplay/android-developer/answer/6334282?hl=en&ref_topic=7072031
I think the confusion comes from the statement "visible on Google Play". It is visible on Google Play, but only visible to people who are in the internal testers list. No-one else can see it or find it in search results.
The benefit to it being "visible" on Google Play are things which require this, like testing in-app purchases or license verification work.
I'm working through the quick-start for a Gmail Addon.
https://developers.google.com/gmail/add-ons/guides/quickstart
When I try to Install my developer addon I
Open the Gmail add-on settings tab
In the Add-ons tab, make sure that you have selected the Enable developer add-ons for my account checkbox
However there is no checkbox...
Is this edition limited? Do we need to do something else to enable this?
Thanks for your help,
Paul C
Apparently there is a bug for GSuite admins and they cannot see that button or add addons right now.
Try your personal gmail for now.
There is an issue open with Gmail https://issuetracker.google.com/issues/68234732
I have contacted the Gsuite team, will update the answer once I have something solid.
Update (Dec 19, 2018)
Looks like this issue has been fixed, I could get it working on Corporate and Personal email.
According to this recent G Suite Developers Blog post, installing developer add-ons has now been enabled for users of G Suite.
And indeed, when I go to 'Settings' -> 'Add-ons' in my G Suite account, I do now see the 'Enable developer add-ons for my account' checkbox.
However, when I click this and enter my script's deployment id, I always get the same error message: 'Invalid Add-on'.
I would be interested to hear if anyone has got this working or not?
Edit 02/02/2018:
Further to the above and following communication with Google Support, apparently it looks like a setting in our G Suite Admin was causing the problem.
We managed to fix it by following the instructions here, making sure to select 'Allow users to install any application from G Suite Marketplace': https://support.google.com/a/answer/6089179?hl=en
It's a bit counter intuitive that a setting involving the Marketplace should affect our developer plugin that we hadn't yet put on the Marketplace, but in any case, after an hour or so our developer plug-in started to function.
Obviously it also is not ideal having to allow any app to be installed from the App Marketplace. Hopefully Google will put a more permanent solution in place soon.