claude-code - 💡(How to fix) Fix iOS app cannot spawn new remote control sessions (web app works) [1 comments, 2 participants]

The spawn request from iOS is silently dropped. The daemon poll loop never receives a work item for the spawn. No error is shown in the iOS app.

Error Messages/Logs

TL;DR

• The most likely fix involves investigating differences in how the iOS app and web app interact with the claude remote-control daemon, specifically focusing on the spawn/new session functionality.

Guidance

• Investigate the network requests or API calls made by the iOS app when spawning a new session and compare them with those made by the web app to identify any discrepancies.
• Verify that the --spawn=worktree mode is correctly configured and supported for both the iOS app and the web app.
• Check the daemon's configuration and logs for any hints on why the iOS-initiated spawns are silently dropped, focusing on differences in handling between iOS and web app requests.
• Consider testing with a previous version of Claude Code that is known to work, if possible, to isolate the regression.

Example

• No specific code snippet can be provided without more details on the implementation, but an example of how to debug the network requests could involve using tools like curl or a network debugging proxy to capture and compare requests from both the iOS app and the web app.

Notes

• The issue seems to be specific to the interaction between the iOS app and the claude remote-control daemon, suggesting that the problem might lie in how the iOS app communicates with the daemon or in the daemon's handling of such requests.
• Without more information on the previous working version or specific changes made, it's challenging to provide a more targeted fix.

Recommendation

• Apply workaround: Until the root cause is identified and fixed, spawning new sessions from the web app and then resuming them from the iOS app seems to be the most viable workaround.

FAIL-SAFE

Given the information provided, the guidance focuses on investigative steps rather than direct fixes, ensuring a safe approach to troubleshooting without making assumptions about the underlying implementation.