You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So far everything is working for linking to various pages on our SharePoint site (same domain), with one exception: we are linking to a training event calendar on our Learning Pathways site. Part of this calendar includes automatically generated "Add to calendar" links that open an ICS file when clicked. These links show up on all browsers when directly accessing the site, but do not appear in the Teams client (mobile or web) when using the Get Started app.
Is there any known configuration change we need to make to get these links to be available?
The text was updated successfully, but these errors were encountered:
Thanx for this feedback. I do believe that is a known issue with the display of the iFrame inside of Teams but I'm putting this under investigation so we can give you a final answer. @arun-msft please investigate this for us. Thank you
@karuanag: As @arun-msft mentioned the "add to calendar" was working fine with teams when opened in the browser, but when we tried to open it in teams application it was throwing error and loading a blank page.
@J-Krepps-OH: for now, you can use "add to calendar" from browser teams we will get in touch with our engineering team and try to fix the issue as soon as possible in teams app
So far everything is working for linking to various pages on our SharePoint site (same domain), with one exception: we are linking to a training event calendar on our Learning Pathways site. Part of this calendar includes automatically generated "Add to calendar" links that open an ICS file when clicked. These links show up on all browsers when directly accessing the site, but do not appear in the Teams client (mobile or web) when using the Get Started app.
Is there any known configuration change we need to make to get these links to be available?
The text was updated successfully, but these errors were encountered: