Power Platform Community Forum Thread Details

Issue: "At the code level, the freeze occurs the moment the agent reaches any Question node within the Microsoft Copilot iOS app. In our production agent, this is most commonly observed at question_ogaMrA (the hcpStatus = "SINGLE" HCP confirmation), as it is the first Question node hit in the most common flow path. The behavior is reproducible at every other Question node in the flow as well, and was independently confirmed in a stripped-down 3-step demo agent. The issue is not specific to this node's configuration — it is the iOS app's handling of the user input handoff."

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.

Categories:

Calling actions from Copilot Studio

Hello AA-11051353-0 ,

Greetings! Thanks for raising this question in the Q&A forum.

Thank you for the incredibly detailed and well-documented report this is exactly the kind of evidence that helps pinpoint a platform regression quickly. Based on everything you have shared, this is clearly a client-side regression in the Microsoft Copilot iOS app introduced with the April 2026 mobile redesign, specifically in how the new chat input composer handles the user input handoff at Copilot Studio Question nodes. The agent-side and server-side are working correctly the freeze is happening in the iOS app's input layer, not in your agent logic.

Here is what we recommend as your next steps:

Step 1: Raise a Priority Microsoft Support Ticket Immediately

Since you are a Microsoft Employee and this is a confirmed version-specific regression affecting a production agent, escalate this through an internal support channel or via the Microsoft 365 admin center support ticket path. In the ticket, include:

Affected app version: 2.109.26043033 (post-April 2026 — broken)
Working app version: 2.109.26042215 (pre-April 2026 — working)
The stripped-down 3-step demo agent reproduction steps (this is your strongest evidence — a minimal repro in a clean environment rules out all agent complexity)
Confirmation that web (Chrome) and all non-iOS channels work correctly
Confirmation that Adaptive Cards and EndConversation nodes are not involved

Step 2: Use the Demo Agent Repro as Your Official Bug Report Artifact

The minimal 3-step demo agent is your most powerful asset here. Package the repro steps clearly ideally a short screen recording on the broken version vs. the working version side-by-side and attach it to your support ticket. This eliminates any chance of the issue being attributed to your production agent's configuration.

Step 3: Provide Users a Temporary Workaround

While the fix is in progress, direct affected iOS users to one of these options:

Use the Microsoft Copilot web version (via Safari or Chrome on iOS) as a stopgap you have confirmed this works correctly
If your organization manages devices via Intune or an MDM solution, check whether you can pin or roll back the Copilot iOS app to the pre-April version (2.109.26042215) for affected users temporarily

Step 4: Test on Android

You noted Android was not tested. It would be worth running the same minimal demo agent on Android to determine whether this is iOS-only or affects the broader mobile app redesign. If Android is also affected, this significantly strengthens the urgency of the bug report.

Step 5: Monitor the Power Platform and M365 Message Center

Keep an eye on the Microsoft 365 Admin Center's Message Center and the Power Platform admin center for any service advisory or known issue postings related to the April 2026 Copilot mobile redesign. Microsoft's engineering team typically posts acknowledgment there once a regression is confirmed on their end.

Your investigation is thorough and the evidence is conclusive this is a platform bug, not an agent configuration issue. The priority right now is getting it in front of Microsoft's iOS app engineering team with your clean repro.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,
Jerald Felix.