mobridge-mcp 0.10.2 → 0.10.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (12) hide show
  1. package/AI-USAGE.md +2 -1
  2. package/dist/main.obf.cjs +1 -1
  3. package/dist/protocol/schemas/action.schema.json +1 -1
  4. package/integrity.json +2 -2
  5. package/loader.cjs +1 -1
  6. package/package.json +1 -1
  7. package/resources/android/app-developer-release.apk +0 -0
  8. package/skills/VERSIONS.json +4 -4
  9. package/skills/mobridge-companion-setup/references/upgrades.md +1 -0
  10. package/skills/mobridge-core/SKILL.md +3 -0
  11. package/skills/mobridge-debugging/SKILL.md +3 -2
  12. package/skills/mobridge-debugging/references/connection-errors.md +2 -1
package/AI-USAGE.md CHANGED
@@ -57,7 +57,8 @@ After an install/update, connect waits for the companion to become ready (a few
57
57
  | ACCESSIBILITY_DISABLED | The Accessibility service is off. | self-heals / retry | Run `mobridge connect`; it enables the service over adb and reads it back. |
58
58
  | ACCESSIBILITY_ENABLE_BLOCKED | The phone does not let adb enable the Accessibility service. | needs action | Show the user `userAction`, then run `mobridge connect --wait-user 120` to resume the moment it is on. User: Settings > Accessibility > MoBridge Runtime > On. Android 13+: first Settings > Apps > MoBridge Runtime > ⋮ > Allow restricted settings. Xiaomi: Developer options > USB debugging (Security settings). |
59
59
  | WAITING_FOR_USER_ACCESSIBILITY | Waiting for the person to turn Accessibility on; the wait window ended. | needs action | Ask the user to finish the step, then run `mobridge connect` again (it resumes; nothing is reinstalled). User: Settings > Accessibility > MoBridge Runtime > On. |
60
- | ACCESSIBILITY_PREEMPTED | The service is enabled but not bound; another owner took the session. | self-heals / retry | Wait a few seconds and run `mobridge connect`. |
60
+ | ACCESSIBILITY_PREEMPTED | The service is enabled but Android shows it unbound (the OEM killed it, or an install left it half-bound). | self-heals / retry | Run `mobridge connect`: it switches the service off and on once and retries. If it repeats, check `dumpsys accessibility` for another service or UiAutomation. |
61
+ | ACCESSIBILITY_CRASHED | Android lists the MoBridge accessibility service under Crashed services; it is not running even if it looks enabled. | self-heals / retry | Run `mobridge connect` (it toggles the service off and on). If it repeats, toggle MoBridge Runtime in Settings > Accessibility. |
61
62
  | EXTERNAL_INSTRUMENTATION_ACTIVE | Another tool holds UiAutomation (uiautomator, a test runner, another agent). | needs action | Fail fast: ask the user to stop the other tool, then `mobridge connect`. User: Stop the other automation tool on this phone. |
62
63
  | TRANSPORT_DEGRADED | The link to the phone dropped. | self-heals / retry | Retry the read; for a mutation check `mobridge operation status <operationId>` first. Prefer USB over wireless adb. |
63
64
  | WS_CONNECTION_LOST | The WebSocket to the companion closed. | self-heals / retry | Reads retry by themselves; a mutation reports RESULT_UNKNOWN, so look its operation up, never resend it. |