-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect Context Returned by getContext()
in Multi-Account Environment on Teams Desktop Client
#2462
Comments
Hi yuezk! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies. Best regards, Teams Platform |
getContext()
is messing up in multi account environment.getContext()
in Multi-Account Environment on Teams Desktop Client
@yuezk - Thanks for raising your issue. We are checking the issue. and we will get back to you shortly. |
@yuezk, we tried to repro this issue in MS Teams desktop client (Windows) with version Microsoft Teams version 24193.1805.3040.8975(The client version is 49/24071128823.) having multiple accounts, however we are getting desired result. The context returned corresponds to the active logged-in account only. |
I encountered this problem randomly. You could try to add another account from other tenants. For me, I added my work tenant, then I added some accounts from my 365 developer tenant to test the custom app. It will get the context info of my work tenant last week. Then I signed out all the accounts and re-logged, now it will get the context from my 365 developer tenant but the user info is incorrect. I can reproduce it on my Mac, but my colleague has encountered this problem on Windows. The video below shows the problem that the context is from my work tenant while the active account is the 365 developer account, which is totally wrong. 8.14.mov |
Hi @yuezk, we added account from another tenant and tried to repro this issue, still it worked as expected for us. Although we don't have any repro still, we have raised a bug for this issue and engineering team is looking into it. We will inform you once we get any further update. Thanks! |
Description
When using the Teams Desktop client with multiple accounts, the
getContext()
function often returns the context of an incorrect, non-active account. This behavior occurs despite the correct account being active in the client.My Teams client version: macOS, 24193.1707.3028.4282 (24193.1707.3028.4282). This issue is also reproducible on Windows.
Steps to Reproduce
Demo video attached in #2462 (comment)
Open the Teams Desktop client and log in with multiple accounts.
Ensure one account is active.
Use the following code to retrieve the context of the active user:
Observe the context returned.
Expected Behavior
The context returned by
getContext()
should reflect the active user account in the Teams client.Actual Behavior
The context returned often corresponds to a different logged-in account rather than the currently active one. For example, when the active account is
[email protected]
, the context returned might instead show information from[email protected]
.Code Example
The full code to reproduce this issue can be found here.
Screenshots
Here’s a screenshot showing the issue, where the context of the wrong user is displayed:
The text was updated successfully, but these errors were encountered: