Open vhensorskyi opened 8 months ago
Thanks for reporting this! I tried to repro the issue but was successfully able to call microsoftTeams.authentication.getAuthToken
and get a token from within the pop-up authentication window (which had a frame context of authentication
.)
I am able to see the place in the code where the "App webApplicationInfo or resource not defined in manifest" string is defined, but it doesn't seem like it should be triggered in this scenario.
Could you provide some more details so I can investigate further and help?
webApplicationInfo
section, but if you could confirm this, that would be great.authentication.authenticate
and then calling authentication.getAuthToken
from within that pop-up window (based on your comment about the frame context being authentication
. Is this correct? What parameters is it passing when it calls authentication.authenticate
?getAuthToken
from your app outside of an authentication pop-up (i.e. different frame context) work just fine?Thanks!
Hello,
Thanks for your response.
Web and Mac were used only
Yes, webApplicationInfo is set properly in the manifest
The is initiated from the card:
{ "type": "Action.Submit", "title": "Sign In", "data": { "msteams": { "type": "signin", "value": "${authUrl}" } } }
and the popup has authentication context.
Yes, using the same configuration getAuthToken
fetches tokens fine in different contexts.
Let me know if any additional info is needed.
Thanks for the additional info. Triggering the authentication window from a card is likely the difference in how we are trying to reproduce the problem. Can you tell me more about how the card is being provided to Teams? E.g., is it being returned from a bot? Or a message extension?
Yes, it's an adaptive card shared by a bot in a personal conversation.
Thanks; with this information I was able to repro the problem. I will investigate and report back here.
Hi,
Is there any progress on this?
Thanks for checking in; I'm still working with the team responsible for the likely problematic code to identify the issue and understand their plan for the fix. I don't know of any workarounds, unfortunately.
Thanks for the info. Please keep me posted.
After reproducing the problem and debugging it based on your helpful information, it looks like the problem is in the Teams app itself (and not the application platform) so @nwojod-MSFT will transition the tracking of this issue to the folks who help with issues in Teams.
For reference for others: the issue only repros when the authentication pop-up is triggered from an adaptive card. It does not occur when the authentication pop-up is called from teamsjs using authentication.authenticate
.
Thank you. FYI, it also reproducible from the messaging extension cards :(
@vhensorskyi - We have raised a bug for the same. We will inform you once we get any further update from engineering team. Thanks!
Hi @vhensorskyi -- I just wanted to give you an update: I talked with the developer in Teams responsible for the code with the issue and they've coded up a fix for this and it's out for code review. I'll provide more updates as I have them.
Hi @vhensorskyi - We got update from engineering team that the fix has been merged. Please do verify and let us know.
Hi @Prasad-MSFT,
Thanks for getting back. I've just tested the flow again and it doesn't seem to be working properly. Now instead of Cannot get authorization url App webApplicationInfo or resource not defined in manifest
the function throws Error
without any details. Please see a screenshot for reference. It was verified on web teams v2.
Hi @Prasad-MSFT ! Having the same issue, it is just Error: Error
for us though.
It is failing in authentication
context and in getAuthToken
as well, as we can see in our Sentry dashboard.
Thanks for letting us know. We have informed the same to engineering team. Once we get any update, we will notify in this thread.
Hi,
We have been using teams-js library
2.6.0
and noticed thatawait microsoftTeams.authentication.getAuthToken({ silent: true })
call fails withCannot get authorization url App webApplicationInfo or resource not defined in manifest
inmicrosoftTeams.FrameContexts.authentication
but works fine in other contexts fine. Is it a known issue?Regards, Volodymyr