microsoft-graph-toolkit icon indicating copy to clipboard operation
microsoft-graph-toolkit copied to clipboard

[BUG] mgt-login not signing in, in Team Desktop client. Uncaught (in promise) undefined.

Open StanDEV1234340t98 opened this issue 2 years ago • 3 comments

Describe the bug I'm using the Microsoft Graph Toolkit Login React component in a Microsoft Teams Tab. And the Teams desktop client behaves differently than the Teams web client. See screenshots below. The desktop client doens't have the loginFailed/loginCompleted events when the signin popup closes and stays on the sign in button. But when i refresh the page it changes to the person card, and i'm signed in. Also i see an "Uncaught (in promise) undefined in string.ts.10.

To Reproduce

  1. git code : https://github.com/StanDEV1234340t98/testauthentication
  2. in the index.js add a clientId
  3. use ngrok to host the code and open the page in a teams tab.
  4. try to sign in.

Expected behavior I would expect the desktop client would behave the same as the web client.

Screenshots Web client webclient

Desktop client desktopClient

Environment (please complete the following information): Browser: Chrome, teams.microsoft.com Desktop: Windows, Microsoft Teams client, Version 1.5.00.9567 (64-bit).

StanDEV1234340t98 avatar Apr 13 '22 12:04 StanDEV1234340t98

Hello StanDEV1234340t98, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

ghost avatar Apr 13 '22 12:04 ghost

Hello @StanDEV1234340t98, I'm trying to reproduce this. In the meantime, is there any particular reason you're not using TeamsMsal2Provider?

musale avatar May 04 '22 12:05 musale

I would highly advise to use the TeamsMsal2Provider as it handle all this beautiful magic for you!

sebastienlevert avatar May 09 '22 17:05 sebastienlevert

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.