Forum Discussion
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.
jocsch​ : Have you been able to overcome this issue? We are trying the same and run into the same problem.
In the meantime, we have been 1 step further:
Context:The app is running locally in our dev tenant. This dev tenant is also the publisher of that app.
Steps:
In the teams admin center, we will manually overwrite the manifest of that dev app with our dev manifest.
Then under permissions, we will grant all permissions via admin.
What we achieved so far:
- app will load with right version and permission.
Where we are struggling right now:
* Nothing happens :-D No activity is send although the graph api accepts our request.
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.