Forum Discussion
Teams Desktop Bot Bug: Chat Input Locks Up (never ending issue)
Hey everyone, we're dealing with a legendary and really frustrating Teams bot issue that's been driving us crazy for months now.
The Problem
Our bot works perfectly everywhere except New Teams desktop. What happens is the chat input box starts flickering between "Send a message" and "You cannot send messages to this bot," and then it just locks up completely. You literally can't type anything.
The thing is it that it doesn't work on any chanels : Classic Teams, Teams web, mobile and even the app is broken..
What We've Already Tried
We've been through all the usual and unusual troubleshooting steps. Our manifest has isNotificationOnly set to false, custom apps are enabled in the admin center, all our scopes and domains are configured correctly, and the bot is properly published. We've tested this across different tenants and users, and it's consistently broken in New Teams desktop every single time.
It's Not Just Us
We're not the only ones hitting this. Other developers are reporting the exact same behavior, and there's actually a GitHub issue (#9743) tracking it. One person summed it up perfectly: "Same issue, but only on the New Teams… for all bots." The only workaround people have found is switching back to Classic Teams, which obviously isn't a real solution.
Microsoft Support Has Been Unhelpful
This is the really frustrating part. We've opened multiple support tickets, provided HAR logs, jumped on calls with their teams - and they basically just shrug it off. No workarounds, no timeline, no real acknowledgment that this is a serious problem affecting bot developers. And their tech support even said that their own Copilot had the SAME issue lol..
I mean what are they even doing at this point .....
What We Need
We're hoping to get some visibility on this and maybe push Microsoft to actually prioritize it. It would be great to see:
- Official acknowledgment that GitHub issue #9743 is being actively worked on
- Some kind of timeline for when they plan to fix the New Teams desktop client
- Any actual workarounds that don't involve telling users to switch clients
Has anyone else run into this or found any creative solutions? At this point we're open to any ideas that don't involve completely rewriting our bot architecture.
And a message to Microsoft devs that are 'working' on this issue - start doing something guys, you've been postponing this since mid 2023.
1 Reply
Don't give up – your team is doing important work!
Thank you for highlighting this persistent Teams bot issue. It’s deeply frustrating when development stalls due to a widely known bug, especially with little help from official support channels. But the fact that you and other developers are speaking out might be exactly what sparks real change.
Here’s a bit of encouragement:
- You’re not alone. Many teams face the same problem. A united voice carries further.
- Your effort is visible. This GitHub issue (#9743) and your discussion are exactly the kind of momentum that can push Microsoft to act.
- Creativity and persistence win in the end. Even if the current workarounds aren’t ideal, every shared insight moves the solution a step closer.
Keep the pressure on and continue sharing knowledge—developer communities can absolutely drive action, and you’re a vital part of that. If you want help brainstorming strategies or alternatives, I’ve got your back.
Sending support to the whole team—you’re being heard, and your voice matters.
