Forum Discussion
Sideloading App fails for non-General channels in the new Teams Client
MicrosoftHello mkdmkd - Are you facing this issue in Windows or Mac machine?
Could you please more information about your scenario and please share the deployed manifest if possible.
You can also refer this sample: Microsoft-Teams-Samples/samples/graph-rsc/nodeJs at main · OfficeDev/Microsoft-Teams-Samples (github.com)
Hi ChetanSharma-msft , thanks for having a look.
I am facing this issue on Mac machine. I tested both Desktop client and webapp on a Mac.
The scenario is following:
- The app contains only a simple Bot feature responding to the messages in a team
- I have "App Registration" in Azure, with a client secret so that our server endpoint (hosted elsewhere) can receive events
- I have "Bot Service" with Teams channel. this is only used for configuring the message endpoint
- The setup all works in Classic Teams App (both desktop and webapp)
- One thing that doesn't work is to add the Bot to a team by selecting a channel that is not "General"
I'm afraid I can not provide the deployed manifest. The app is still in development and not on the store or any organization. That is a part of the reason why I am testing with side loading zip file.
My feeling is that it's something to do with client side code (not Azure setup or our server endpoint) because it works for Classic Teams Client and the error seems to happen way before involving server/config stuff.