Troubleshooting
Look up by symptom. Most issues are found in logs or error text in the task panel.
AI Agent window won't open
Symptom: Clicking "AI Agent" in the new control center does nothing.
Check:
- Install directory has
aibinfolder and AI programs inside (usually bundled with installer) - Open
aibin/log/, checkjavaexec-iosagent-ui.logfor errors - Windows first run may need WebView2; installer folder often has installer, or install from control center menu
- Antivirus blocking
Shows not connected
Symptom: Toolbar says AI service offline.
Check:
- Click "Start AI"
- Check
aibin/log/javaexec-iosaiagent.logfor errors - If still failing, close AI window and reopen from new control center
Can only type list workflows, can't chat normally
Cause: LLM not configured, or wrong key / API URL.
Fix:
- Click "Model config", confirm API URL, model name, API key
- Toolbar should show current model name
- Corporate network blocking external APIs (proxy, firewall)
AI says it can't find a workflow
Fix:
- Refresh workflow library on the left
- Ask AI to “list all workflows”, or confirm name in library
- If newly created, save in editor first
Device license failure
Symptom: Task error about license; device_auth_ok fails in chat or flow.
Fix:
- Confirm USB device license purchased and bound (not screen license) → Prerequisites & licensing or USB screen tutorial · Purchase license
- Confirm phone online in new control center device list
- Replug USB, or check proxy App / automation service
- Refresh license in control center License Center
- If flow has “license check” step, confirm correct type (USB device license / screen license)
Can't start automation / tap or screenshot fails
Symptom: ensure_auto_env fails, or automation screenshot / tap no response.
Fix:
- Per Prerequisites & licensing: IPA signed and installed, bundleID configured, developer disk image ready
- Enable automation in control center until service status is Yes; right-click device Test automation for logs
- Details: USB screen tutorial · Sign IPA, Start automation
- If you only need screenshot/OCR without automation, use Non-automation screenshot/OCR steps or chat commands
BLE step failure
Symptom: ble_click etc. fail in workflow.
Fix:
- Complete Bluetooth/OTG setup in Prerequisites & licensing
- Control center Bluetooth HID settings → Test Bluetooth BLE
- See BLE tutorial, OTG tutorial
Screenshot fails in chat
Symptom: “Automation screenshot” fails.
Fix:
- Say “Start automation environment” first, then screenshot
- If you don't want automation, use “Non-automation screenshot” or “Non-automation OCR”
Both screenshot types use the same names in chat and workflows: Non-automation screenshot / Automation screenshot.
OCR slow first time or slow again after task ends
Cause: OCR engine loads per device + engine type; released after formal task ends; next run re-initializes.
Fix:
- Consecutive OCR in one flow reuses engine — much faster from second time
- Editor OCR preview keeps engine loaded — good for debugging
- Don't mix many
ocrTypevalues casually — each type uses separate memory
Image match / color-offset match no match
- Confirm template path relative to working directory, or re-crop template in Match preview
- Non-automation image match needs no automation; automation image match needs Start automation environment first
- Transparent/color-offset templates: use color-offset match step, not plain template match
- Tap offset wrong: add Match data extraction (center) then tap, don't use top-left coordinates directly
See Image/color matching.
Can't open App / automation won't start
Suggested order (add steps in flow or ask AI to follow):
- Reset USB connection
- On Windows try USB flash disconnect (like unplug), then wait 5–10 seconds
- Start automation environment, wait until ready
- Open App again
Still failing: expand task in Task panel, see which step failed and error text.
Workflow save / validate failure
- Click Validate, read first red message
- Common: missing path, flowchart not connected to end, subflow reference missing
- Check params against Workflow step reference
Can't pick device for trial run
- Need online device in new control center
- Refresh device list in editor trial run bar
External CLI won't run
- In CLI/MCP integration, confirm added and name matches
- Check
aibin/log/api-error.log
Data stored in wrong place
Expected:
- Business data:
aibin/data/aiagent/(or directory you set in Settings) - Logs:
aibin/log/
If paths wrong after upgrade, use 10.1.0+ new control center and AI components.
Log locations
| Content | Path |
|---|---|
| AI service | aibin/log/javaexec-iosaiagent.log |
| AI window | aibin/log/javaexec-iosagent-ui.log |
| API errors | aibin/log/api-error.log |
Task panel or control center Open AI log directory opens aibin/log/ in one click.
Many devices run slowly
- Increase Max devices per task in Settings, then restart AI
- One phone cannot run two tasks at once
Version info
AI Agent window status bar shows version and build time.
Still stuck
Prepare:
- Relevant logs from
aibin/log/ - Task ID (copy from task panel)
- Problem workflow (workflow library → Open folder, copy files)
- New control center version, reproduction steps
Provide all when contacting support.