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.
Related
I have published a Google Apps Script as a web app. Because the URL is not so nice, I have included the script in an iframe on a site with a nicer URL. I have included the corresponding option so that it works at all. Now this web app should only be accessible within the Google Workspace (formerly known as GSuite) I am working in. This setting can be done when publishing the Web App. The problem is, however, that some users (by far not all users!) in our Google Workspace cannot access the Google Apps Script that way. There is a error message saying that Google prohibits the connection.
It seems like the authenticiation does not work "through the iframe". Interestingly, the problem only arises when
the script is embedded in an iframe (the direct script URL by Google works for the users)
the script is restricted to the Google workspace.
Chrome is used (the issue does not happen with Firefox)
It is remarkable that for most users in our Google Workspace the issue does not appear. We had similar problems when including the script on a Google site (which, in the end, is also just an iframe), but with less users experiencing the issue. I have already made sure that the users are only logged in with their Google Workspace account (no other account which has no permission). In Inkognito mode the same happens.
Can someone explain this behaviour? And how to fix that (without changing the framework)?
I have been in contact with the Google support. If I remember correctly, this kind of authentication will be deprecated and should now be done with other tools, for example Google's Firebase Auth.
My Google App Script (an add-on for Google Docs) has passed the OAuth verification and has also been verified by the Google team. The application is both "Published" and "GAM: Published", yet Domain Admins are unable to locate the add-on when searching for it, and therefore cannot install it to their domain users.
I have read the following two articles many times:
https://developers.google.com/gsuite/add-ons/how-tos/publish-addons
https://developers.google.com/gsuite/add-ons/how-tos/publish-for-domains
I've been liaising with the docs-addon-advisor, who has approved the add-on again and again, but nothing seems to impact the Marketplace Apps search results. It is however availble in the Web Store search results. They have directed me back to this forum for advice.
I've followed the articles above and see no error messages in the publication, yet still the add-on remains invisible to the Domain Admin world.
You can see that DocuSign is happily installed in my domain, I can search for it, and it has been pushed down onto my domain users. So what I'm trying to achieve is possible. My add-on is simply absent from this marketplace search for some reason.
Any ideas?
Your add-on is published at https://gsuite.google.com/marketplace/app/seal_atn/820114923602. It does not have "Enable individual install" checked so it's installable and searchable only by domain admins.
I'm using free Google Apps subscription and I've published self-made extension in Chrome Store. Also, I need to restrict access to that extension to only my domain users.
I tried to follow Google manual, but I couldn't get access to 'Device management > Chrome management' (got an unexpected redirect from 'Device management' page to Apps list while clicking on 'Chrome management' link) and there was no option 'everyone at mydomain.com' into extension 'Visibility section' — only 'trusted testers'.
So, maybe it's because of my free subscription or it's Google Apps issue or I do something wrong?
No, That feature (and process) is only available for Google Apps for work and Education accounts.
However, you can try to restrict access to your chrome extension (using your free account) before publishing it to public by publishing it to test accounts.
Publishing to test accounts
When you publish to test accounts, your app’s store listing only appears to you and any users who are logged into these test accounts that you specify. Your app won’t appear in search results, so you’ll need to give testers a direct link to your app’s listing. Testing also gives you a chance to see how the license server integrateswith your app if you plan to charge your it using Chrome Web Store Payments.
To edit your list of accounts, click Edit your tester accounts. You can enter single accounts, or create a Google Group so that this set of users can test your app. See the section below to learn how to set up Group Publishing.
Once you’re ready to publish, click Publish to test accounts.
You’ll need to unpublish the app if you want to publish to the world later.
I'm trying to publish a Google Docs addon, visible only to my Google Apps domain, and then automatically install it for everyone in the domain
I have:
made a script in Google Drive, shared it with everyone on the domain
deployed it to the Developer Dashboard using Publish -> Deploy as Addon, with Publish in Google Apps Marketplace turned OFF
pushed it from the Developer Dashboard, making it visible just to users of my domain, giving it all the necessary fields and images
verified that others from the domain can install the addon by going to Addons -> Get addons in a Google Doc, toggling the filter to For mydomain.com. Also verified that it works when installed that way.
created a new project in Google Developers Console, added Google Marketplace SDK and created an OAuth2 client id
I'm stuck on the step of "configure Marketplace SDK", specifically the project key for the Docs add-on extension option in it, where I'm consistently getting a Project Key is not associated with current project. error.
I believe I need to finish this step, so that I could then re-do step 2 with Publish in Google Apps Marketplace turned ON, and then finally enable it for everyone.
Steps that shouldn't affect things, but might be worth noting:
I am not the owner/admin of the domain, but the admin is assisting in steps where I get stuck. (like creating the OAuth2 client id)
I have transferred ownership of the Developer Dashboard entry to a group that I'm owner of (on the desired domain)
I have transferred ownership of the Developer Console project to that same group
the problem was I manually created a project in Google Developers Console
instead, I should've used the Resources -> Advanced Google Services -> Google Developers Console link to access a HIDDEN PROJECT (?!) and enable Marketplace SDK there.
sigh.
I made an app as an extension on Chrome Web Store. I would like to know the download count for my extension.
From the developer's dashboard I can access to Statistics, but the graphic starts in 21/5/2015 (three months ago) and the CSV file too.
How can I see the complete download history?
Creating a Google Analytics account using it to track installs is probably a pretty close estimate of downloads.
Once you create your Analytics account, you create a new property with the default URL being your extension page. For example, https://chrome.google.com/webstore/detail/<extension-name>/<extension-id>
Once you get your tracking id, add that to the edit page for your extension in the webstore developer dashboard.
Once you have done that go to the Analytics admin panel and on the right click Goals. Add a new Custom goal of Destination type for the RegEx match of /track_install/.*.
You can now add a graph of this goal completion to track installs.
Here is a comparison of the data collected by Google Analytics and the Statistics in the webstore developer dashboard.