Trying to DELETE Add-Ons that have been added to the G-Suite Market Place - google-apps-marketplace

We have been developing a Sheets Add-On for the first time and during that process we created a couple of "test" Add-Ons and published them to the G-Suite Market Place. We are now ready to publish the "production" version of the Add-On.
I want to delete those "test" Add-Ons as they may be confusing to the users of the Add-On in our domain. I have contacted Google Support for G-Suite and they have not been able to help with this....
See the screenshots that show the Add-Ons that I want to delete from the marketplace....I have been able to un-publish them but they are still appearing in the listings for our domain as available to install.
Any help on this would be appreciated.

I work in the G Suite Marketplace. I've asked the Chrome Web Store team and they said they don't support deleting listings, but you can unpublish them.
As you may know we are in the process of migrating G Suite extensions from CWS to GSM (Chrome extensions will remain in CWS). Unpublished CWS listings will not be migrated to GSM and some time after March 10, 2019 we will delete all G Suite extensions from CWS.
For more background, please visit the Chrome Web Store migration page for editor add-ons or for Drive apps. If you have additional questions or need assistance, please contact CWS migration support.

Related

Publishing partially enabled Add-Ons In Google Marketplace

We are currently developing GMAIL addons in our company.
My question is very simple. Does the google apps marketplace allow the publication of Partially Enabled add-ons?
We were thinking of using a service like LaunchDarkly to be able to turn some features on and off for some or all of our clients.
Thank you very much.
PS : Partially enabled addons, operate only with say 40-60 percent of their functionality upon download. If a corresponding feature flag is activated on our end or in a service like LaunchDarkly, they will be 100% operational (or feature complete).
Depending on the functionalities you want to enable and the type of add-on you have, you might be able to make use of Editor add-ons triggers or Workspace add-ons triggers and limit the interactions based on these.
However, an add-on must be fully functional before it is published.
Reference
Publish an Add-on;
Editor Add-on Triggers;
Google Workspace Add-on Triggers.

Developing an integration of my company's product with Microsoft Teams using connectors

I am a Software Engineer and working on developing an integration of my company's product with Microsoft Teams. The idea is that the product will send messages/notifications/alerts to a chat channel in Microsoft Teams. At the moment we are only working towards developing this integration with Microsoft Teams and not other office 365 products.
After researching on MSDN, Microsoft developer platform, google etc. I came to know that I can set up an incoming webhook which gives me a URL against a channel in Microsoft Teams and I can send messages to it. However, I came across another method which is having a connector in the Microsoft store. I would like to add a connector because it provides a nice front end and also gives us a presence on the store for external users. I found out that I can register a connector from the connector developer dashboard. Here is the documentation link that I was referring to:
https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/connectors
To test it out I referred to the following example on the MSDN blog:
https://blogs.msdn.microsoft.com/mvpawardprogram/2017/01/24/part-3-office-365-groups/
However, I am unable to see Microsoft Teams groups in the drop down. I am the owner of these groups on Microsoft Teams side. At my organization only I am using Microsoft Teams to test this integration because I am the only developer working on this. Please, see the screenshot below:
Then I read about sideloading your connector to Microsoft Teams to test it out which meant uploading the manifest.json file from the connector developer dashboard. Please, see the below screenshot:
But, after I download the manifest file and follow the instructions mentioned on this link https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/apps/apps-package I am still running into problems testing the office 365 connector with Microsoft Teams when uploading the manifest file. This is the error that I get, please see the screenshot below:
Also, I do this from my developer trial account and this is because from my company's paid developer enterprise account I do not see an option to upload a custom app. Please, see the screenshot below:
This is a product issue and I have been in touch with the product support for the past three weeks. We have tried various things over this course of time and nothing has worked. They have also ran recovery diagnostics on my account as well but, I saw no changes. All they tell me is that "this is bizarre, this should not be happening and that maybe Teams is a fairly new product and nobody develops for it etc. etc. " Although I do feel many enterprises are using it. Please, see the screenshot below:
I have not heard back since then. Please, help me regarding this issue. I would really love to start developing the actual integration with our product since it would be of great value to our customers.
Thanks,
Maria Shoaib.
Please use App Studio to create manifest file and test your connnector so that there are no errors while creating an app package. Also, please ask your tenant admin to enable the sideloading of external apps for Upload Custom App link to appear in Microsft Teams.

What happens to my Xamarin app after my subscription expires?

Currently I am working on a Xamarin project which is basically a college news app (just like newspaper apps like "Times Of India" etc). I have used Microsoft Azure for updating news blogs.
My question is when my Xamarin subscription expires, will my app continue to work or not?
Actually, if you buy any of the annual licenses, you are free to continue to recompile and develop. It is only the monthly indie licenses that prevent development if you do not renew. In either case your built app will not be affected
The app itself will continue to work but you will not be able to recompile if you dont reactivate the Business licence

App has been unlisted from Google Apps Marketplace

I had my app in the marketplace for around an year and recently found it was unlisted. I think it might be because one of the instances of the app was using the old API. I fixed it but found no way to inform Google so the listing could be activated again.
Today, I found that the listing has completely been deleted from the marketplace.
Can someone help sharing insights on what might have happened or what is the process to bring back the listing? Or perhaps how to reach out to someone at Google to help resolve this?
Many Thanks
The Google Apps Marketplace V1 (GAM v1) is being deprecated, during this process the applications that were not migrated to the new version (GAM v2) were unlisted.
Here you can find information about the GAM v2 and how to publish your app in this new platform. https://developers.google.com/apps-marketplace/
One difference is that the new listing version runs under Chrome web store https://chrome.google.com/webstore/developer/dashboard

WP7 - selling extensions

I'm trying to create some application for Windows Phone >= 7.1
During plannin my work and specyfiong technical requirements I've come across one problem.
I wan't to have free application with basic functionality. And then it should be extendable with some non-free extensions (dlls?, databases?, SaaS?)
Is it possible at the moment to use some MS api/app/etc. to be able to publish such extensions and sell them? What is the best way to do this if there is more than one solution?
Thank you for any help.
As of right now (June 2012), in-app purchases are not supported. Your only choices, then are being a paid app and supporting trial mode.
The only way you can do this at present is to handle the additional purchases yourself.
You'd have to set up a website which customers could create an account on and purchase extensions through, then have them also log into your app with those account details to determine what additional data to download or functions to enable.
You could be smart and include the website functionality into your app with a browser control. Take a look at the Amazon Kindle app for an example of how they accomplish it.

Resources