I have created a Teams App with the App Studio. When I install it with App Studio everything is working? I am now trying to publish the app to the tenant app store
I have downloaded the app packaged from App Studio and uploaded the package to the Teams admin portal. The package uploads without any errors and the app is shown in the catalog list as a custom app
I have enabled
“Allow third party app”,” Allow any new third party apps… ” “Allow interaction with custom apps” on ”org-wide app” settings
-the global Permission policy I have “Allow all apps” on the three subjects
-the Global Setup Policy I have “Upload custom apps” and ”Allow user pinning” on
But my app does not show in the catalogue in the Teams client
After adding and removing the same police, restarting the client multiple times and waiting 48 hours- The app now show up in the catalog
Related
I created an SPFX application with the Teams Toolkit that utilises Microsoft Graph API to get data,after packaging and deploying the manifest folder to Teams Admin Center, it renders well with accounts that have Teams Admin and Global Admin access but accounts without this access are unable to access the application as it shows an error as seen in the image.
The Component ID and version in the message are speaking to the React-dom component id and version in the project.
Please i need suggestions on how to resolve this as i am not sure if its just a permission issue
I have tried updating my spfx version but that didnt work as i was already working with the required version of spfx and all other dependency versions
You can raise an issue in https://github.com/OfficeDev/TeamsFx/issues so we can support you better.
I tried to reproduce your issue but failed. The web part displays successfully for account without Teams/Global Admin in my side. Let's clarify the steps before the issue happens:
Create a SPFx project in Teams Toolkit and utilizes Microsoft
Graph API to get data
Click 'Provision in the cloud' to provision
the Teams app (with Teams/Global admin account)
Click 'Deploy to
the cloud' to generate the sppkg and deploy it to SharePoint (with
Teams/Global admin account)
Click 'Publish to Teams' to publish
the Teams app manifest in Teams app catalog (with Teams/Global admin
account)
Approve the submission in Teams admin portal
Install
and open the Teams App in Teams with Teams/Global admin account and
the web part displayed successfully
Install and open the Teams
App in Teams without Teams/Global admin account and the web part
shows error.
Could you help confirm whether you're having the steps above to reproduce the issue?
BTW, after deploying you should be able to use the web part with normal account in regular page in SharePoint. Maybe you can check whether everything is OK in SharePoint app catalog
SPFx solution after deploy to SP app catalog
I am trying to use contentBotId (Azure bot ID) in my MS Teams manifest file.
https://learn.microsoft.com/en-us/microsoftteams/platform/resources/schema/manifest-schema-dev-preview
When it is from same tenant that of MS teams domain (xyz.com) then its working and loading the data
But when its from different tenant, then MS Teams is not loading anything
{errorCode: 0, message: "<BadArgument>Unknown bot"}
Is there any restriction on this?
Before creating the MS bot, using ML Studio, create multi-tenant bot for perfect App registration.
Follow the procedure to create the bot and register the application.
By mentioning all the required. Check the manifest file for the required ContentBotId. Test the URL after app registration into multi-Tenant.
If still the error occurs. We need to setup the connection settings under configurations.
By adding Oauth connection settings we will get some kind of authentication for different clients for the same authentication URL (website URL).
Able to resolve the issue.
Yes it can be from different tenant.
when we use existing AAD instead of creating from Azure bot template, this issue occurs. Seems like MS Teams is not able to find this AAD/ or Bot Handle.
Root Cause (Might be): Manually created AAD have email address of user who have created this in Owners section (screenshot 1), while AAD created from Azure bot template have "Bot Framework Dev Portal" user (Screenshot 2).
And I am unable to add this user by searching.
Screnshot 1
Screenshot2
I'm working on a Slack integration for our workspace that is within an Enterprise Grid. I have a workspace and I've created a Slack App with all possible OAuth scopes and have installed it in the workspace.
I'd like to automatically invite and remove users to our workspace using the app/bot. I should be able to do this with the Slack app/bot using the admin.users.invite and admin.users.remove API actions.
However, these two actions require the admin.users:write OAuth scope, which can only be used on an App that is installed organization-wide, so I can't use this scope on my workspace app:
The app requesting this scope must be installed by an admin or Owner of an Enterprise Grid organization. Also, the app must be installed on the entire org, not on an individual workspace.
Is there any other way I can have an automated system that invites/removes users to/from our workspace, without it being an organization-wide app? This is something I can do as a user through the Slack UI (and I'm not an organization admin, just a workspace admin), so one would think I should be able to do the same things via an app/bot that is installed and authorized to act on my behalf.
Unfortunately, the APIs currently provided by Slack are available for Org Owner & Org Admin roles.
The best course of action for you will be to collaborate with your org admins. Let them manage the app. It means you will not have access to token, but you can use the app as a user.
Create the app that will operate only on your workspace by using fixed teamId.
Ask the org admin to generate the admin token and update that in your app.
May be, if they find your app useful, it can be used across organization eventually.
After generating APK definition file, i tried to publish it on play console by following below reference
Reference : Publish an externally hosted app in the Play Console
step-1) Sign in to the Play Console with your organization's administrator account.
step-2) Create a private app by publishing to your own organization. Ensure you add at least one organization to Private app access.
step-3) Click Upload external APKs.
Issue : In step-2 we need to create new app in play console. I'm unable to create new app when login play console with enterprise account(Not an Android Developer Account) create app button is noneditable, do i need to add any other settings to make it editable.
You need to have android developer account for creating apps, there is a fees of 25$ to create developer account.
Unfortunately, you cannot use your enterprise account to create apps in the Play Developer Console, you need to have a Google Play Developer Account to do this. However, you can use the following steps to create an externally hosted app:
Upload an apk via iFrame with the same app id as the app you want to host externally. This will essentially act as a “dummy” app.
Generate a JSON metadata file using the steps described here. Make sure that the version of this externally hosted apk is higher than the one uploaded via iFrame.
On the iFrame, click the app and open the Play Developer Console via the “Make advanced edits” button.
Create a new release by navigating through the sidebar, then Production > Create new release.
Upload your JSON metadata file under “App bundles and APK”.
Then, Save > Review Release > Start rollout to production.
We migrating our app from the old Marketplace to the new one. And we faced with the problem like described here - Google Apps Marketplace app installation callback
But we have special app architecture, it allows to the same user authorize multiple domains. For example we have user(authorized with google +) admin#tester1.com and he needs to install app for following domains:
tester1.com where admin account is admin#tester1.com
tester2.com where admin account is admin#tester2.com
For tester1.com we can use licensing API and check if app is installed and who installed it. We already have authorized account admin#tester1.com and the same user installed app.
No issues for this scenario.
Next user needs to install app for tester2.com. In process of installation(at the marketplace side) user switching to new account admin#tester2.com and installing app.
When user backs to us, we using licensing API again and check if app is installed and who installed it. At this step app will be installed, but it will be installed by user admin#tester2.com which is currently not connected to our app.
For this scenario, how we can securely recognize that domain tester2.com should be linked to user admin#tester1.com? Any recommendations/advices?
Currently we see only one way - require user to authorize admin account for each domain that he wants to install with our app.
This appears to be a special case, and Google don't have any guidelines around how to handle it. Deciding how to charge for and provision your application is left up to the developer.