Root Cause: We believe Microsoft Copilot iOS app regression introduced in the April 2026 mobile app redesign. The redesign included a new chat-first layout and updated input composer, which no longer integrates correctly with Copilot Studio Question nodes. The native send/record button freezes the moment the agent reaches any user-input step. Confirmed by: users on the pre-April 2026 version work fine; users on the latest version are affected. Does not look to be code issue.
What was investigated:
ENVIRONMENT
- Platform: iOS (latest version)
- App: Microsoft Copilot (2.109.26043033 - Post-April) — BROKEN
- App: Microsoft Copilot (2.109.26042215 - Pre-April) — WORKING
- Channel: Copilot Studio agent surfaced via Microsoft Copilot app
- Web version (Chrome): Working correctly
- Android: Not Tested
KEY EVIDENCE
1. PRODUCTION AGENT: Identical agent and payload works correctly on the pre-April 2026 iOS app version and on all other platforms. No changes were made to agent code between working and non-working states. All server-side activity logs show successful execution.
2. STRIPPED-DOWN DEMO AGENT: To rule out any complexity in the production agent, we built a minimal 3-step demo agent in a clean Microsoft environment using the latest Copilot Studio. This minimal agent reproduces the exact same issue — works on desktop (Chrome), fails on the latest iOS app at the first Question node requiring user input.
3. Adaptive Cards are not in use — ruled out as a cause.
4. EndConversation node is not a factor — the freeze occurs before the flow ever reaches the End Conversation node. (However, we can test)
5. The issue is version-specific and platform-specific: users still on the pre-April 2026 iOS app version are fully unaffected.
6. Timing aligns directly with the April 2026 Microsoft 365 Copilot iOS mobile app refresh that introduced the new chat input layout.

Report
All responses (
Answers (