Skip to content
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

iOS Outlook - tenant id is provided in upper case #2192

Open
onmomo opened this issue Feb 29, 2024 · 5 comments
Open

iOS Outlook - tenant id is provided in upper case #2192

onmomo opened this issue Feb 29, 2024 · 5 comments

Comments

@onmomo
Copy link

onmomo commented Feb 29, 2024

When accessing the tenant id injected by the useTeams() react hook, context.user?.tenant?.id returns the tenant id in all upper case (e.g. 3A0B3C51-3E1D-44F1-BA8E-9F82B6880005 )which is not the case if the app is called outside of the iOS Outlook context where we receive the tenant always in lower case.

Copy link
Contributor

Hi onmomo! 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

@maglims
Copy link
Contributor

maglims commented Feb 29, 2024

Hi @onmomo, thanks for reporting! Could you please help us to understand the issue a little more here? Is the issue just a matter of upper case vs lower case difference, or the value of tenant.id don't match when calling outside of ios outlook (ignore the case)? Thanks!

@onmomo
Copy link
Author

onmomo commented Feb 29, 2024

Hi @onmomo, thanks for reporting! Could you please help us to understand the issue a little more here? Is the issue just a matter of upper case vs lower case difference, or the value of tenant.id don't match when calling outside of ios outlook (ignore the case)? Thanks!

The value is correct. Doing a to lower case fixes the issue. Note, this seems only necessary when the app is loaded with iOS Outlook.

@maglims
Copy link
Contributor

maglims commented Feb 29, 2024

ok, thanks for the extra info! We will look into more and get back. Thanks.

@maglims
Copy link
Contributor

maglims commented Mar 4, 2024

Just as update, the relative team has identified the bug and will be working on solution. We will update the build number once it becomes available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants