iOS remote app: stranded scroll-to-bottom chevron makes AskUserQuestion Submit button non-interactable after foregrounding from push notification

Platform

Claude Code remote control iOS app (mobile companion app).

Summary

When an AskUserQuestion prompt arrives via push notification while the app is backgrounded, foregrounding the app from the notification leaves the keyboard in a broken state: the keyboard itself is gone, but the scroll-to-bottom chevron ("down arrow") stays stranded in the middle of the screen. Everything below that stranded chevron becomes non-interactable — including the Submit button — so the question cannot be answered. Unless I scroll all the way up so the content is above the area where the keyboard was shown earlier.

Steps to Reproduce

1. In a session, start typing a prompt so the keyboard is visible.
2. Background the app (the keyboard was up at the time of backgrounding).
3. While backgrounded, the agent calls the AskUserQuestion tool, which fires a push notification.
4. Foreground the app by tapping the push notification.

Expected Behavior

The AskUserQuestion sheet is fully laid out and interactive. The keyboard (and its scroll-to-bottom chevron) is either properly restored or fully dismissed, and the Submit button is tappable.

Actual Behavior

• The keyboard is no longer present, but the scroll-to-bottom chevron / down arrow remains floating in the middle of the screen, occupying roughly where the keyboard's top edge used to be.
• The region below the stranded chevron is not interactable — taps don't register.
• The Submit button (and the "Other" option / lower options) sit in that dead zone and cannot be pressed, blocking the user from answering the question.

Impact

The question prompt is unanswerable from the app — the user is fully blocked on that turn until the app is force-restarted or the session is otherwise reset.

Environment

• App: Claude Code remote control (iOS)
• OS: iOS
• Trigger: AskUserQuestion tool push notification while backgrounded with keyboard previously visible

Attachments

_Screenshots demonstrating the issue are attached below._

<img width="460" height="895" alt="Image" src="https://github.com/user-attachments/assets/6a86a62f-2dbb-4bb5-9adc-aa952c6258f0" />

<img width="460" height="895" alt="Image" src="https://github.com/user-attachments/assets/2b9608b9-430f-45a7-a24b-f7014fbcaf26" />