Forum Discussion
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?
Microsoft@jocsch - We successfully added the app using your provided manifest. Could you please check it again and let us know if it is working on your end?
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.jocsch​ : Have you been able to overcome this issue? We are trying the same and run into the same problem.
No, sadly I never found a solution but didn't continue with the feature I wanted to realize.
I still wonder if this is just happening on sideloaded apps and it is working fine the moment it is an official production release. But as we have existing clients I don't want to risk testing it out in practice.
