User Profile
Sayali-MSFT
MicrosoftJoined Nov 01, 2021
User Widgets
Recent Discussions
Re: Web Notifications API from Personal Tab app doesn't work
Hello SGymerATComitFS, Microsoft Teams personal tab apps, even when opened in a popped‑out window, still run inside a controlled WebView environment rather than a full browser, which limits support for APIs like the Web Notifications API. As a result, notifications may appear to work (permissions granted, no errors) but never surface as OS‑level desktop alerts. Because of these platform restrictions, real‑time scenarios like WebRTC alerts cannot reliably use browser notifications inside Teams. The recommended approach is to use a hybrid model—keep the app in Teams for UI and entry, but handle notifications and always‑on functionality in an external browser or PWA, or fall back to Teams‑native mechanisms like bot notifications when external options are not feasible.Re: Web Notifications API from Personal Tab app doesn't work
Hello SGymerATComitFS, Web Notifications created using the standard browser Notifications API (new Notification(...)) do not reliably surface as native desktop toasts when your web app is running inside a Microsoft Teams personal tab—even if the tab is popped out into a new window and permissions are granted. This is because Teams hosts tab content within its own controlled runtime environment rather than a full standalone browser, and that host does not consistently forward web-based notification requests to the operating system’s notification center. As a result, the API may appear supported and run without errors, but no system-level notifications are displayed. The Notifications API is designed to allow browsers to show system notifications outside the web page viewport, but actual delivery depends on the host environment, and embedded shells like Teams may restrict or ignore them for security or platform consistency reasons. Couple clarification questions: Do you need notifications while the user is not actively focused on Teams, or only while Teams is open? Are you able to support an installed PWA (same URL, installable) as the “always-on + notifications” runtime, with Teams acting as the entry point?Re: Issue with Teams 'Add a User to Group Chat' API call?
Hello AutomatonSolutionsRDE, The request fails due to two issues: first, the @odata.type value was misspelled, causing Microsoft Graph to stop processing and return a misleading schema error. Second, an incorrect property was used instead of user@odata.bind. Correcting both issues resolves the problem. The proper request body must include the correct @odata.type, roles array, and the user@odata.bind reference to the target user. { "@odata.type": "#microsoft.graph.aadUserConversationMember", "roles": [], "user@odata.bind": "https://graph.microsoft.com/v1.0/users('USER_ID')" }Re: [iOS] Custom App Icon still renders as white square
Hello XianYunTang, We were able to reproduce the issue in the [Mobile (iOS)] Teams version [7.22.77.2025223902/1219]. We have reported this as a bug for further investigation. We will keep you updated as soon as we receive further information. Thank you for bringing this to our attention!Re: Bot configuration config/fetch returns same channel ID when switching channels within same team
Hello rasharab, Thank you for your patience! We were able to reproduce the issue. We have reported this as a bug for further investigation. We will keep you updated as soon as we receive further information. Thank you for bringing this to our attention!Re: Users on iOS can't write to group chat with a bot
Hello Yannick_Malins , We are pleased to inform you that the bug has been fixed! The fix has been verified in the following versions: Mobile (iOS)Teams Version [7.20.77.2025203102/1113] Please verify on your end and confirm if everything is working as expected. If you encounter any further issues, feel free to reach out. Thank you for your patience!Re: Issue with Teams Tab App
Hello achebrol, Intermittent connectivity issues in a Teams tab app—especially when hosted on AKS—typically stem from network routing, DNS delays, or transient connectivity failures rather than actual app downtime. Because retries usually succeed, the app is likely healthy, but some requests fail to reach it. Troubleshooting should start with checking detailed error messages and network traces in Teams to identify whether the failure is due to DNS, TLS, or HTTP routing issues. Common causes include DNS resolution delays, certificate or TLS problems, ingress or load balancer instability, and client-side proxy or network constraints within Teams. To diagnose the issue, review AKS ingress and application logs, test DNS resolution, examine ingress health, verify SSL/TLS configuration, and use network tracing tools. Potential fixes include lowering DNS TTL, adjusting ingress timeouts, ensuring proper health probes, validating Teams manifest domain entries, and using Azure Front Door or Traffic Manager to improve reliability.Re: Issue with Teams Tab App
Hello achebrol,Thank you for bringing this issue to our attention. To assist you better, could you please provide the following details? Reproduction Steps: Please share the steps you took to encounter the issue. Documentation Links: Any specific documentation you followed that relates to your problem. Teams Client Version: What version of the Teams client are you using? Code Snippets: Relevant code snippets that illustrate the issue. Manifest Package: If applicable, please share the manifest package for your app. This information will help us better understand the situation and provide a more accurate response.
Groups
