Call URL Handler leads to crash in new Teams

Question

I have a problem with an application which we are developing.

This happens only in the new Teams Application.

Basically I need to start an external Program, which is registered in Windows with a specific URL Handler. It worked fine in the old version. The command I use is a simple:

window.open(`myOwnUrlHandler:${u8sSIPAddress}`, "_self");

The error I get is:

Refused to frame '' because it violates the following Content Security Policy directive: "frame-src blob: data: https: acrobat2018: ales: arcb: blocked: bookmark: ciscotel: cloudya: com.bt.cloudwork.app: com.rainbowoffice.app: com.ringcentral.vodafonebusiness.app: companyportal: deltapath-engage: devtools: jamfselfservice: mailto: maxuccall: microsoft-edge: ms-access: ms-actioncenter: ms-appx-web: ms-excel: ms-infopath: ms-powerpoint: ms-project: ms-publisher: ms-settings: ms-spd: ms-teams: ms-visio: ms-whiteboard-preview: ms-word: msteams: notes: odopen: officeathand: onenote: openapp: opentouch: pdf: rcapp: rctelus: sebs: sip: sips: softwarecenter: suknil: tel: unifyoffice: vscode-insiders: vscode: vsls: wazo: webex: webextel: x-apple.systempreferences:".

What has changed? Am I doing something wrong?

Thanks for any suggestion...

chetansharma-msft · Answer

Hello MatthiasAbele - Thanks for raising your query.Could you please share the exact link format that you are using to test window.open?

matthiasabele · Answer

ChetanSharma-msftI call window.open like this:

window.open("test-url-handler:email address removed for privacy reasons", "_self");

test-url-handler is a valid url handler registered in windows. If I call "test-url-handler:email address removed for privacy reasons" from a browser it actually opens the registered application as desired.

Thanks

Matthias

chetansharma-msft · Answer

Hello MatthiasAbele - Thanks for sharing the information.
This issue is because of violation of Content Security Policy in Teams.
So, we will confirm with engineering team and let you know the updates whether it is not supported or a bug.

vikram-mfst · Answer

Hello MatthiasAbelewe have got an update from our engineering team.We've always had that CSP header in place for the Teams Web Client (T1 and T2.1); it's now also in effect for the New Teams Desktop Client (T2.1). This header is necessary to ensure the security. If you need to launch out to a native app via a custom protocol, you can use any one of these options:1)Call window.open with target parameter set to "_blank" instead of "_self".2)Use an anchor tag with target="_blank"3)Call the https://learn.microsoft.com/en-us/javascript/api/@microsoft/teams-js/app?view=msteams-client-js-latest#@microsoft-teams-js-app-openlink or https://learn.microsoft.com/en-us/javascript/api/@microsoft/teams-js/?view=msteams-client-js-latest#@microsoft-teams-js-executedeeplink SDK API

matthiasabele · Answer

Thanks,vikram-MFST&nbsp;Very valuable information. For all 3 options you gave me, the link is now working fine, no crashes.But:1) tel:+0000000000 is working2) test-url-handler:email_address is NOT working&nbsp;on 1) the correcty registered handler for tel: is calledon 2) nothing happens. When I use the openLink call, the Promise is correctly fulfilled, no errors thrown, but no URL handler outside is called.&nbsp;Any idea?&nbsp;Thanks a lot 🙂&nbsp;&nbsp;

Forum Discussion

Call URL Handler leads to crash in new Teams

9 Replies

Resources