Skip to content

[macOS][BlueStacks hd-adb] Tasker not properly initialized after ADB push/pull failures (exit 6/1) #1289

@Windsland52

Description

@Windsland52

问题类型 / Issue Type

一般 Bug / General Bug

问题描述及复现步骤 / Problem Description & Reproduction Steps

Expected:

  • After selecting the saved BlueStacks device and starting tasks, Tasker should start normally.
  • If some ADB methods are unsupported, framework should gracefully fallback instead of failing task startup.

Actual:

  • Task startup fails immediately with: Tasker not properly initialized.
  • Before failure, ADB connect/get-state works, but several key ADB commands fail repeatedly:
    • shell settings get secure android_id (exit 1)
    • pull /data/local/tmp/... (exit 6)
    • push maatouch/minitouch to /data/local/tmp/... (exit 6)

Reproduction Steps:

  1. Use M9A-macos-aarch64-v3.23.2-MXU with MaaFramework v5.10.2 on macOS (arm64).
  2. Auto-detect and connect BlueStacks device emulator-5554 using /Applications/BlueStacks.app/Contents/MacOS/hd-adb.
  3. Start a preset task set (e.g., Daily profile with multiple tasks).
  4. Observe immediate failure: Tasker not properly initialized.

MaaFramework 版本 / Version

v5.10.2

日志文件 / Log Files

M9A-logs-v3.23.2-20260421-150816.zip

Important evidence lines:

Pipeline JSON

崩溃 Dump 文件 / Crash Dump (仅崩溃问题 / Crash only)

No response

Draw 调试图片 / Draw Debug Images (仅识别问题 / Recognition only)

No response

模板图片 / Template Images (仅识别问题 / Recognition only)

No response

其他信息 / Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions