Closed xrajishx closed 3 years ago
I had a call with someone from the Microsoft support team and got this issue resolved. Apparently I did have problems in my configuration. I am closing this issue, but I think it helps to have some error message displayed somewhere that will help us debug when there are issues in our OAuth configuration instead of it having it not show any errors and also not work.
Linking to answers.microsoft.com where I posted what worked for me, so that people can find it if they face the same issue as I did.
Versions
What package version of the SDK are you using.: ~4.14.0 What nodejs version are you using: v14.15.1 What browser version are you using: Chrome What os are you using: MacOS Catalina
Describe the bug
OAuth cards from OAuthPrompt do not render within teams app. It works fine within the Bot Framework Emulator and within 'Test in Web Chat' option in the Azure bot page in Azure portal. It does not however show the login card within the teams web app or within teams desktop app.
To Reproduce
Steps to reproduce the behavior:
ngrok
for a https url./api/messages
as the messaging endpoint.teamsAppManifest
with the correct ids and zip the contents of the folder and upload as a new app in teams. Test the behavior in teams web and teams desktop.Expected behavior
The login prompt card shows up just like it did on the emulator and the web test chat feature.
Actual behavior
The prompt never shows up. If you already login from a different client, you will get auto logged in. But if you logout with the 'logout' command and try to login again, the prompt does not show up.
Screenshots
Works in Bot Emulator
Works in Test in Web Chat
Does not work in teams
Additional context
Looking into it a bit more, I see the prompt card that is sent just sends an activity with the content below. Without using OAuthPrompt, if you simply use
sendActivity
to send this object from your bot, it behaves the same way (works everywhere except in teams).