Description

I'm experiencing an issue with the latest version of mobile-mcp where the tool fails to initialize properly. Rolling back to version 0.0.19 resolves the issue, suggesting there might be a problem with the most recent release.

Environment

• OS: macOS (darwin 24.5.0)
• Shell: zsh
• Node.js: (installed via npx)
• mobile-mcp version: @latest (causing issue), 0.0.19 (working)

Bug Report

Current Configuration (Causing Issue)

mobile-mcp:
    command: "npx"
    args: ["-y", "@mobilenext/mobile-mcp@latest"]

Error Details

• Error Message: Error: spawnSync ios ENOENT
• Symptoms: mobile-mcp tools fail to function properly
• Impact: Unable to use mobile device control features

Working Configuration (Rollback Solution)

mobile-mcp:
    command: "npx"
    args: ["-y", "@mobilenext/mobile-mcp@0.0.19"]

Test Results with v0.0.19

• ✅ mobile-mcp initializes successfully
• ✅ Android device detection works properly (detected device: R3CR50MWDSL)
• ✅ Mobile automation features function as expected

Observations

Version Comparison

• v0.0.19: ✅ Stable and working
• @latest(0.0.20): ❌ Currently causing spawnSync ios ENOENT error

Possible Cause

The error message suggests there might be an issue with iOS-related dependencies or spawn processes in the latest version.

Request for Investigation

Could you please verify if there are any known issues with the latest version? I noticed that v0.0.20 was recently released with several improvements including:

• New save_screenshot tool
• New use_default_device tool
• iOS WDA support improvements
• Android UTF-8 text support

It's possible that one of these changes might have introduced a regression.

Additional Information

The rollback to v0.0.19 works perfectly for now, but I'd like to use the latest features when they're stable.
Thank you for maintaining this excellent tool!

Note: This report was organized with AI assistance (including AI opinions)