Forum Discussion
Windows App iOS RemoteApp Won't Reconnect
We are building a RemoteApp environment using AVD for the session hosts.
On iOS, what happens is the screen powers off/device goes to sleep.
When a user logs back into the iPad, the RemoteApp was still the focus, so they see buttons to reconnect or disconnect. If we press reconnect, it will either spin endlessly OR it will report an error on reconnection attempt.
If we then close the error OR if we press disconnect where it drops us into the Windows App, then reopen the exact same Windows App it immediately reconnects.
This does not happen in Windows at all, we have no Android deployments to test, and are trying iOS deployments on iPad and troubleshooting with iPhones. Both device types experience the issue.
To troubleshoot, I've tried multiple iOS devices by multiple users; same problem.
Those same users connecting to our AVD desktops, not RemoteApps, reconnect without issue.
Our AVD and RemoteApp session hosts all use the same Group Policies and are, at this point, only domain joined, not Entra or Hybrid.
Any thoughts on why this happens? Would logs be helpful?
1 Reply
This pattern looks client-side rather than host-pool configuration: the session remains reconnectable, and only the iOS RemoteApp UI gets stuck after suspend. Microsoft’s current Windows App known-issues page doesn’t list this exact behavior, so I wouldn’t change GPOs or rejoin hosts yet.
First update Windows App and iOS/iPadOS, then run Windows App > profile icon > Health Checks immediately after wake. For a useful trace, go to Settings > Troubleshooting, set Core and UI logging to Verbose, start logging, reproduce sleep/wake/reconnect once, then stop and export the files. Record the Windows App and iOS versions, UTC time, error code, and any Activity or Correlation ID.
On the Azure side, enable host-pool and application-group diagnostics and compare that timestamp in WVDConnections, WVDErrors, and WVDCheckpoints. If the failed tap creates no new connection event but reopening the app does, that strongly isolates the defect to the iOS client. Submit those logs through Windows App feedback or Microsoft support; until then, disconnecting and reopening is the cleanest workaround.
