I have a Microsoft teams custom app which is already available to customers on teams app marketplace. We have upgraded the manifest version and next step would be to submit the application for production release.
Once Microsoft approves it, How will this app be available to end users since admin approval is required for app update?
In our version upgrade no new permission set is added but how will it be visible in both:
If no new permission is added?
If there are new set of permissions are added?
Will there be a prompt from teams end?
According to the official document, it shows that when you do some changes for custom app in Teams admin center, it will take up to 24 hours for the end users to see the changes. You can try to wait for 24 hours to see if it can change.
For more details, you can refer to:
https://learn.microsoft.com/en-us/microsoftteams/customize-apps#frequently-asked-questions
In most cases, after you complete an app update the new version automatically appears for end users.
However, there are some updates to the Microsoft Teams manifest that require user acceptance to complete.
For more details, you can refer to:
https://learn.microsoft.com/en-us/microsoftteams/upload-custom-apps#end-user-update-experience
Related
I have a question regarding installation of messaging extension app. Actually I assumed that I can upload my app to teams admin center "teams apps" and afterwards it is ready to use for all teams and all team members. I already did this steps with an app showing a custom tab and everything worked fine.
Across the documentation I only found information on how to sideload apps. That is working but only for the logged in user, not for other team members. Thats why I think app package seems to be ok.
So, what is the correct way to install an app containing a messaging extension to my teams so that all team members can use it? Does app manifest need to provide some special content?
Thanks for your help!
Yes, Admin has the privilege to install an app from the admin center by assigning custom policy to users. Please have a look at this document.
We recently added a QnA Maker Bot to MS Teams and got it to Deploy on the Azurewebsites.net/api. Unfortunately in MS Teams when you direct message the bot it is not responding at all. We checked the logs and are not getting any errors either. Any Idea where we need to check next?
Thank you,
M
I had exactly this problem, and it was because I was trying to hit the bot directly rather than creating a Teams App first. You will need to install App Studio from the Apps blade on the left if you haven't already.
Open up App Studio and click on Manifest editor tab
Click Create a new app
Fill our all of the required information for App details
Generate/create an App ID. This is NOT the same as your Bot's App ID
Click on Bots tab under Capabilities and add your bot
Install app for testing in specific Teams or Chats
Submit is for if you want to publish to your company's App Store. If you download the package you could import it in Step 2 instead of creating a new app. Or use it as a template to do future apps offline instead of using App Studio for the whole process.
Once I set up the bot in this way, it started responding to me. I tried with another app after doing this for one and confirmed that I would NOT get a response from a bot unless I had set it up with a manifest through App Studio.
I am trying to build a Teams tab using an SPFx web part for a demo.
On my inital app the Sync to teams button in the app catalog was failing with this console error being returned...
https://{TENANT}/sites/AppCatalog/_api/web/tenantappcatalog/SyncSolutionToTeams 400
After running into this problem I started again and this time followed the below tutorial step by step but on my tenant the Sync to Teams button is disabled (This step is near in the end in the Making the web part available in Microsoft Teams section)
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/using-web-part-as-ms-teams-tab
I then tried to follow the alternative method of side-loading the app by creating a manifest manually using this tutorial...
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/guidance/creating-team-manifest-manually-for-webpart
This resuted in the installation succeeding as far as the setup tab screen (this provides a preview of your tab in a model popup before adding the tab to a channel)
The result was "Sorry, something went wrong" (This was the end result of side-loading both my customised web part another freshly yo sharepoint generated scaffold.
Really stuck on whether there's a tenant issue or maybe some node package or SPFx version issue.
Any thoughts would be greatly appreciated.
I received a same error from console which led me to this article.
In this case, the app was already synced to Teams store. If that's the case, you should find and remove it by opening Teams -> Apps -> Built for [tenantname]. After removing it here, I am able to successfully sync my app once more.
I'm using SPFx 1.8.1 version and added TeamsTab in supportedHosts manifest file. Deployed in tenant app catalog and tried to Sync to Teams. Then I'm getting same issue of SyncSolutionToTeams with 400 error. Please find the attached screenshot from console windwow.
The error occurs if the app is still in the Teams catalog. It doesn't override it and instead throws the error. This is a known bug and we will look to fix it in the future. For now, please try either manually updating the app from Teams (not from the SharePoint app catalog) or to delete the Teams app and then to resync from SharePoint.
In my case this error occurs when I changed title in webpart manifest file (webpart.manifest.json). When I rejected the change, it works. Probably there was some inconsistency in project files.
We have successfully moved to the new Google Apps Marketplace using Omniauth2 etc. Yesterday our app got approved by Google. In our listing on the Marketplace the new Chrome Webstore Item Id is in place. But when I want to make any changes to the listing it says: "Vendor is not one of the owners of the current listing". The app still has the old Consumer Key, Application ID etc. From the documentation inserting the Chrome Web store ID should be sufficient. So basically we still have to app versions with two Applications running.
What else is needed to migrate completely to the new version?
If you proceeded with the migration of your app from Marketplace V1.0 to Marketplace V2.0, the application in the old market place will be listed until the Marketplace is completely deprecated. It is no longer possible to edit the listing on the old Marketplace, only editing the new listing under the Chrome Developers Console (https://chrome.google.com/webstore/developer/dashboard).
Keep in mind that the new Marketplace will run independently from the old Marketplace. The new one runs under the Chrome Web Store, and the ids for each store are completely independent. You cant link the old app to the new id.
A few weeks ago, we completed the approval process to get our app listed in the Google Apps Marketplace. It does appear on that site and all is fine. However it is not listed in the contextual Apps Marketplace widget in the Google Apps admin console.
I've read in another post that since November 19th the Apps Marketplace has a new back-end based on the Chrome Web Store, and that only the apps added since then appear in the contextual widget.
So my question is: what will happen to the apps listed in the "old" Marketplace? Will they get automatically migrated to the new back-end at some point? Or do we need to start over the whole publishing process again using the new Marketplace SDK?
We will be launching an API in a few weeks to allow developers to automatically move the domains that installed the legacy (OAuth 1/OpenID) based apps to the new Chrome Web Store (and OAuth2) based Apps Marketplace.
In the mean time, the first step is to create a new listing using the GAM SDK following the steps in the docs so that new domains can install the modern app and then you can migrate the older domains when we launch the API.
https://developers.google.com/apps-marketplace/