User Profile
jocsch
Brass Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Re: RSC permissions cause app to fail installation in personal scope
Nivedipa-MSFTThanks for trying. That is totally strange, that it works for you. I tried it again in my dev tenant and I still get the same error message that I described. If it works for you, then my tenant might be broken. Or it only happens on an upgrade from a manifest without RSC to an manifest with RSC? What really is strange that it works for you. I tried to install it into a second tenant via sideloading and I got this error message on this attempt: {"errorCode":"WebApplicationInfoIdOfSideloadedAppMustBeInTheSameTenantAsUser"} I couldn't find any configuration error and you obviously can install it. I am really lost here, I can't get the very same manifest to work in any of the tenants that I try.Re: RSC permissions cause app to fail installation in personal scope
Nivedipa-MSFTBut that would, that I most likely hit a bug in Teams because without that permission I can install the app, with the permission I can't. Nothing else changes, code is not even reached, it is purely the manifest that has changed in between the installation attempts. So that is a very strong indicator that I hit a bug in Teams. How to proceed?Re: RSC permissions cause app to fail installation in personal scope
Nivedipa-MSFTThanks for your answer. I read this page multiple times but there is nothing, that suggests that some permissions are incompatible with the personal scope. And this doesn't really make sense as it would make it impossible to install an app into multiple scopes which is quite a common thing? You speak of a common issue. Is there any other source where I can read more about it?RSC permissions cause app to fail installation in personal scope
I am trying to update an existing up to send notifications. The plan is to use RSC permissions for it. I configured the manifest (v 1.19) with the following scopes: "authorization": { "permissions": { "resourceSpecific": [ { "name": "TeamsActivity.Send.Chat", "type": "Application" }, { "name": "TeamsActivity.Send.Group", "type": "Application" }, { "name": "TeamsActivity.Send.User", "type": "Application" } ] } }, I then sideloaded it successfully with this configuration into a team and also into a chat. However when I try to install it into the personal scope directly I get the error in a dialog box: Something went wrong In the network tab of the web inspector I see that this call fails with 403: https://teams.microsoft.com/api/mt/emea/beta/users/apps/definitions/appPackage The body of the response says: {"errorCode":"WebApplicationInfoIdConflictOnSideloadingIntoTeam"} However, when I change the included permissions in the manifest to only TeamsActivity.Send.Group the app installs successfully into personal scope "authorization": { "permissions": { "resourceSpecific": [ { "name": "TeamsActivity.Send.Group", "type": "Application" } ] } }, So I guess it has nothing to do with an id conflict. I also made sure to remove all old instances of the sideloaded app before (which was never a problem so far). How can I use all three RSC scopes in my app manifest and still install the app into the personal scope. Or what could be wrong? Anything I could check to figure out why this is not working but only the TA.Send.Group scope?Pinning personal apps via policy for every user
I get reports from customers who setup policies to pin our app to the left sidebar of their users and install it to everyone, but for whom it does not work consistently. I tried it myself and pinned some apps (Praise is among them) in my "Global (Org-wide default)" setup policy. Turns out, that for some test users in my development account this change takes effect but for others it doesn't work at all. No pinned app appears. Even not after waiting 24h and a relogin. So pinning is very random/spotty. This is troublesome as our clients normally want to roll out the app to everyone. I am sorry, that I can not be more precise. I have not figured out why it is broken for some users. I can just offer to help debug with a "broken user" at hand.Re: Task Dialog is not properly closed after submit on Teams Mobile
Prasad_Das-MSFT Thanks for looking into it. I sent the screencasts to the dev community mail address. Sadly I do not have a minimalistic sample as this issue is a bit more involved with server and client components playing together. I already tried to break the explanation down to the most basic parts of the intercommunication. Is this sufficient?Task Dialog is not properly closed after submit on Teams Mobile
The review team of Microsoft stumbled upon a behaviour in my app that shows only in the mobile version. So I think it is a bug. Let me try to explain it, as it is a bit more difficult to provoke. My app opens a task dialog (HTML content) from an adaptive card message via task/fetch. When the javascript inside that dialog is submitted via the dialog.url.submit API, the server responds with a continue task and another html dialog. When this is then submitted, the second dialog is closed but the first dialog is still open. On the web and the desktop the behaviour is different, there both dialogs are closed. I guess this is the expected result, as for both dialogs submit was called. This is in detail what happens: When the user clicks on the action button in the adaptive card, a task/fetch message is send to the backend like this: { "name": "task/fetch", "type": "invoke", .... "value": { "data": { "commandId": "oppenDialog", "type": "task/fetch" }, "context": { "theme": "default" } } } The server response with a continue message to open the HTML based URL: { "task": { "type": "continue", "value": { "title": "Edits", "height": 250, "width": 380, "url": "https://xxx", } } } The page is opened, the user does his work and finally in the dialog this API call is made: msTeams.dialog.url.submit({ commandId: "openSecondDialog", }); According to the API doc, this call is supposed to send the command back to the server and close the task. This is happening on the desktop and the web but not on mobile. (But only, if the server response with another task request). This is the command the server receives when the dialog submits: { "name": "task/submit", "type": "invoke", ... "value": { "data": { "commandId": "openSecondDialog" } } } And this is the response to open the second dialog: { "task": { "type": "continue", "value": { "title": "Open second dialog", "height": 300, "width": 800, "url": "http://xxx", } } } In the second dialog msTeams.dialog.url.submit is called to submit, resulting into another task/submit message to the server which then response with an empty request and status code 200. This leads to the seconds dialog being closed. But on mobile the first dialog is then still visible (which should have been closed after the first submit). Sorry for not being able to break it down any further. As I said, the behavior is not consistent here between desktop and mobile. I think the desktop version shows the correct behaviour. BestMentioning of a user is split in first and lastname
I just discovered that from somewhere in December I do not get a mentioned user in a message as one mention any longer but splitted into two mentions with first and lastname. Is this a bug or is it by intention? This is how the JSON message to the bot for the message: @bot Sarah Johnson mentioning looked like until December: { "text": "<at>bot</at> <at>Sara Johnson</at> mentioning", "textFormat": "plain", ... "recipient": { "id": "...", "name": "bot" }, "entities": [ { "mentioned": { "id": "xxx", "name": "bot" }, "text": "<at>bot</at>", "type": "mention" }, { "mentioned": { "id": "123", "name": "Sarah Johnson" }, "text": "<at>Sarah Johnson</at>", "type": "mention" }, ... ], ... } And this is how it looks today. { "text": "<at>bot</at> <at>Sara</at> <at>Johnson</at> mentioning", "textFormat": "plain", ... "recipient": { "id": "...", "name": "bot" }, "entities": [ { "mentioned": { "id": "xxx", "name": "bot" }, "text": "<at>bot</at>", "type": "mention" }, { "mentioned": { "id": "123", "name": "Sarah" }, "text": "<at>Sarah</at>", "type": "mention" }, { "mentioned": { "id": "123", "name": "Johnson" }, "text": "<at>Johnson</at>", "type": "mention" }, ... ], ... } The mentioning is split in first and lastname with the same userid. Is that the intended behaviour?Re: Can't update the app registration for my teams app
ChetanSharma-msft Let's start with the change I want to do: I open the App Registration of Kudozza in Azure Portal. Then I directly open the Manifest which gives me the json manifest of the app registration. At the end you'll find "signInAudience": "AzureADandPersonalMicrosoftAccount", This is what I change inline to "AzureADMultipleOrgs" No other changes are made. I press "Save" and get the mentioned error. Why do I need to do this? Because I need to add a redirect URL that contains a query parameter and according to the documentation that is only possible for AzureADMultipleOrgs and changing an existing app registration to to AzureADMultipleOrgs can only be done directly in the manifest.Re: Can't update the app registration for my teams app
Meghana-MSFT Nope. I try to change the signInAudience to AzureADMultipleOrgs as this is required to make newer Teams SSO provider work. But it doesn't really matter which property I change. I also tried to change some description but no change is accepted. I just have tried to update the signInAudience again. Maybe you see this in the logs?Can't update the app registration for my teams app
I need to change the EntraID app registration manifest in order to change the signInAudience property. When I try to save the manifest, I get the following error: "Failed to update XXX application. Error detail: No other properties may be modified when certification properties are being modified." Which certification is meant here? The last update of the teams app referencing the app registration was months ago so there shouldn't be an ongoing certification at the moment.Re: User consent: Graph permissions
Ok, after caches cleared I can confirm that it is still a two step process even with admin consent involved. I get the first dialog asking only for the "teams" permissions and and need the second consent for the additional graph permission. If admin consented are involved, the user can not consent the second dialog but has to wait for admin approval. But still two dialogs where I would like to have just one for the user.
