SOLVED

Microsoft Teams custom apps stopped working properly‎.

Copper Contributor

I have been developing Microsoft Teams custom apps since last year and they were working fine. But recently (probably after the recent Microsoft Teams update in March), my custom apps stopped working properly.

 

When my apps try to use Fetch API to connect to my server (node-app) that I have deployed on Microsoft Azure, I get the error "Failed to fetch". Then I tried using axios instead of Fetch, but got the error "Network Error". I also tried upgrading npm packages but couldn't fix this problem.

 

In fact, this phenomenon ONLY occurs on "Teams App on Desktop". The custom apps work perfectly fine on Teams on Browser and Teams Mobile App.

 

Any possible solutions or suggestions are highly appreciated. Thank you!

4 Replies
@FM16-BETA- We are looking into this I will get back to you soon.

@Sayali-MSFT Thank you for your reply. I appreciate your cooperation.

@FM16-BETA -We are unable to repro the scenario. Could you please share the repro steps ,Error log and manifest.so we can can try it from our end?
best response confirmed by Sayali-MSFT (Microsoft)
Solution

@Sayali-MSFT Sorry for the late reply.

Thank you very much for investigating this issue, but after some research and testing, I seemed to have solved the problem.

I am using Helmet (https://www.npmjs.com/package/helmet) for the server (node-app) that I have deployed on Microsoft Azure and apparently, downgrading the version of Helmet from 5.0.2 to 4.6.0 has fixed the problem. On Teams App on Desktop, probably if a Teams custom app tries to connect to a node-app that has Helmet of version 5.0.2, Helmet somehow denies the access and the error occurs.

Therefore, I will be using Helmet of version 4.6.0 for the time being to avoid the error from occurring.

Once again, thank you very much for your kind support!

1 best response

Accepted Solutions
best response confirmed by Sayali-MSFT (Microsoft)
Solution

@Sayali-MSFT Sorry for the late reply.

Thank you very much for investigating this issue, but after some research and testing, I seemed to have solved the problem.

I am using Helmet (https://www.npmjs.com/package/helmet) for the server (node-app) that I have deployed on Microsoft Azure and apparently, downgrading the version of Helmet from 5.0.2 to 4.6.0 has fixed the problem. On Teams App on Desktop, probably if a Teams custom app tries to connect to a node-app that has Helmet of version 5.0.2, Helmet somehow denies the access and the error occurs.

Therefore, I will be using Helmet of version 4.6.0 for the time being to avoid the error from occurring.

Once again, thank you very much for your kind support!

View solution in original post