Forum Discussion
RSC permissions cause app to fail installation in personal scope
Microsoftjocsch - It seems like you're encountering a common issue with RSC permissions when trying to install your app in the personal scope. The error WebApplicationInfoIdConflictOnSideloadingIntoTeam suggests a conflict related to the app's permissions or configuration. Here are some steps to help you troubleshoot and resolve this issue:
Ensure that the permissions in your manifest are correctly configured and supported for the personal scope. Certain RSC permissions might have limitations when used in different scopes.
Ref Doc: Resource-specific Consent for Apps - Teams | Microsoft Learn
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?- Nivedipa-MSFT
@jocsch - The TeamsActivity.Send.User permission is designed to send activity feed notifications to users in Microsoft Teams. It should work in a sideloaded application installed in the personal scope of a user.
For more detailed guidance, you can refer to the following documentation: Send activity feed notifications - Teams | Microsoft LearnNivedipa-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?
