MAA 錯誤偵察Playcover 實際視窗最終閃退

[Georgechengtai]

Checkboxes

请确认自己完成了下列必选项之后再进行勾选，若未完成必选项或勾选了"我未仔细阅读"选项将视为自愿接受被直接关闭 Issue

• 我理解 Issue 是用于反馈和解决问题的，而非吐槽评论区，将尽可能提供更多信息帮助问题解决
• 我未仔细阅读这些内容，只是一键已读所有内容，并相信这不会影响问题的处理
• 我填写了简短且清晰明确的标题，以便开发者在翻阅 Issue 列表时能快速确定大致问题。而不是“一个建议”、“卡住了”等
• 我使用的是当前更新版本的最新版, 并已查看版本发布至今的 更新内容, Pull Requests 中尚未发布的更新内容并未提及该 Bug 已被修复的情况
• 我已检查了 常见问题, 公告, 活跃议题, 已关闭议题 确认我的问题未被提及

问题描述

“PlayCover 当前返回了竖屏/不受支持的 1080x1920 画面”触发了 core 的 UnsupportedResolution；随后 MaaCore / MaaMacGui 又把这次失败误当成已连接成功，最终在第一次点击时空指针崩溃。

Version

6.90

日志和配置文件

asst.log
gui.log

配置信息

PlayCover
1920 x 1080
other resolutions also tried

截图或录屏

还有别的吗？

No response

[MaaArknightsBot]

Issue 概要

• issue：#16448
• 版本 / 资源时间：6.90；gui.log 中可见复现时段先后使用了内置资源 辟路之人（2026-04-28 10:04:05）和外部资源 承诺（2026-05-01 09:02:14）
• 模拟器 / 连接配置 / 任务：PlayCover，用户配置写的是 1920 x 1080；日志实际走的是 MacPlayTools，复现时启动的任务主要是 开始唤醒（StartUp）、公开招募（Recruit）
• 相关设置项 / 关键提示文案：正在连接……、模拟器分辨率不支持，请设置为 720p 或更高，且为 16:9 比例、正在运行中……
• 用户现象：PlayCover 实际回传了 1080x1920 竖屏画面，Core 先报“不支持的分辨率”，但 GUI 仍继续进入运行态并启动任务，随后在第一次点击附近触发 SIGSEGV

关键证据

点击此处展开

• gui.log：
  • 2026-05-01 04:22:34：正在连接……
  • 紧接着：模拟器分辨率不支持，请设置为 720p 或更高，且为 16:9 比例
  • 但下一行马上就是：正在运行中……
  • 然后继续：开始任务：StartUp
  • 同样序列在 04:23:50、04:27:14、04:40:48、05-03 07:50:25 多次重复，说明这不是一次性的 UI 误显示，而是稳定复现的状态机错误
• debug/asst.log：
  • 12:22:35.024：ConnectionInfo {"details":{"height":1920,"width":1080},"what":"UnsupportedResolution","why":"Low screen resolution"}
  • 但在同一次复现里，12:22:35.153 已经开始执行 StartUp 任务
  • 12:22:41.230：刚进入 SubTaskStart ... "action":"ClickSelf" ... "task":"GameStart" 后立刻 Signal caught: SIGSEGV (Segmentation Fault)
  • 后续几次复现同样如此：先 UnsupportedResolution，再跑任务，再在第一次点击附近 SIGSEGV
  • 12:57:08 之后改走 adb localhost:5555 / Compatible 时，日志变成 ResolutionGot 1280x720、Connected、ResolutionInfo ... "Normal"，后续任务可以继续跑，说明问题集中在 MacPlayTools / PlayCover 这条链路，而不是资源任务本身
• issue 正文截图与说明：
  • 用户明确描述“PlayCover 当前返回了竖屏/不受支持的 1080x1920 画面”
  • 与 asst.log 中 width=1080,height=1920 完全一致
• 代码依据：
  • Core 在创建缩放代理时，若分辨率低于 720p 或不是 16:9，会先发 UnsupportedResolution 回调，再抛异常：https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/e644e10d80e3d84d07805268fd901fb4c9593c40/src/MaaCore/Controller/ControlScaleProxy.cpp#L15-L42
  • Controller::connect 在 ControlScaleProxy 构造失败时直接 return false，但没有清掉已成功建立的 m_controller：https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/e644e10d80e3d84d07805268fd901fb4c9593c40/src/MaaCore/Controller/Controller.cpp#L222-L275
  • Controller::click / click(Rect) 直接解引用 m_scale_proxy，没有判空：https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/e644e10d80e3d84d07805268fd901fb4c9593c40/src/MaaCore/Controller/Controller.cpp#L156-L165
  • Assistant::connected() 只看 inited()，而 inited() 最终只要求底层 controller 已初始化：https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/e644e10d80e3d84d07805268fd901fb4c9593c40/src/MaaCore/Assistant.cpp#L181-L200、https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/e644e10d80e3d84d07805268fd901fb4c9593c40/src/MaaCore/Assistant.cpp#L429-L431、https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/e644e10d80e3d84d07805268fd901fb4c9593c40/src/MaaCore/Assistant.cpp#L735-L737
  • 对 PlayToolsController 来说，inited() 只要求 socket 打开且拿到了屏幕尺寸；即使尺寸是错误的 1080x1920，这里仍然会返回 true：https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/e644e10d80e3d84d07805268fd901fb4c9593c40/src/MaaCore/Controller/PlayToolsController.cpp#L50-L53
  • MaaMacGui 的 MAAHandle.connect 调用 AsstAsyncConnect(..., 1) 后，只要 AsstConnected 为真就视为连接成功：

    MaaMacGui/MeoAsstMac/Core/Maa.swift

    Lines 78 to 82 in 7eed483

    	func connect(adbPath: String, address: String, profile: String) throws {
    	_ = AsstAsyncConnect(handle, adbPath, address, profile, 1)
    	guard connected else {
    	throw MaaCoreError.connectFailed
    	}

    、

    MaaMacGui/MeoAsstMac/Core/Maa.swift

    Lines 117 to 123 in 7eed483

    	var connected: Bool {
    	AsstConnected(handle).isTrue
    	}
    	var running: Bool {
    	AsstRunning(handle).isTrue
    	}

  • MaaMacGui 在 ensureHandle() 里连接返回后立刻记一条 Running，之后 startTasks() 会继续 append/start 任务：

    MaaMacGui/MeoAsstMac/Model/MAAViewModel.swift

    Lines 223 to 245 in 7eed483

    	logTrace("ConnectingToEmulator")
    	if touchMode == .MacPlayTools {
    	logTrace("如果长时间连接不上或出错，请尝试下载使用“文件” > “PlayCover链接…”中的最新版本")
    	if toolsMode == .MacSCK && !CGPreflightScreenCaptureAccess() {
    	logError("未开启屏幕录制权限，请前往“系统设置” > “隐私与安全性” > “录屏与系统录音”允许MAA访问")
    	}
    	}
    	let connectionProfile: String
    	switch (touchMode, toolsMode, useGzip) {
    	case (.MacPlayTools, .MacSCK, _):
    	connectionProfile = "MacSCK"
    	case (.MacPlayTools, .BGR, _):
    	connectionProfile = "MacBGR"
    	case (_, _, true):
    	connectionProfile = "Compatible"
    	default:
    	connectionProfile = "CompatMac"
    	}
    	try await handle?.connect(adbPath: adbPath, address: connectionAddress, profile: connectionProfile)
    	logTrace("Running")
    	}

    、

    MaaMacGui/MeoAsstMac/Model/MAAViewModel.swift

    Lines 435 to 477 in 7eed483

    	private func startTasks() async throws {
    	status = .pending
    	defer { handleEarlyReturn(backTo: .idle) }
    	var firstStart = true
    	for (index, task) in tasks.enumerated() {
    	guard case .startup(var config) = task.task else {
    	continue
    	}
    	config.client_type = clientChannel
    	tasks[index] = .init(id: task.id, task: .startup(config), enabled: task.enabled)
    	if touchMode == .MacPlayTools, task.enabled, config.start_game_enabled, firstStart {
    	guard await startGame(client: config.client_type) else {
    	throw MAAError.gameStartFailed
    	}
    	firstStart = false
    	}
    	}
    	for (index, task) in tasks.enumerated() {
    	guard case .closedown(var config) = task.task else {
    	continue
    	}
    	config.client_type = clientChannel
    	tasks[index] = .init(id: task.id, task: .closedown(config), enabled: task.enabled)
    	}
    	try await ensureHandle()
    	for task in tasks {
    	guard task.enabled else { continue }
    	if let coreID = try await handle?.appendTask(task.task) {
    	taskIDMap[coreID] = task.id
    	}
    	}
    	try await handle?.start()
    	status = .busy

  • MaaMacGui 收到 UnsupportedResolution 目前只是 logError("ResolutionNotSupported")，并不会把连接流程判失败或阻止后续启动任务：

    MaaMacGui/MeoAsstMac/Core/MaaMessage.swift

    Lines 48 to 80 in 7eed483

    	private func processConnectionInfo(_ message: MaaMessage) {
    	guard let what = message.details["what"].string else {
    	return
    	}
    	switch what {
    	case "Connected":
    	break
    	case "UnsupportedResolution":
    	logError("ResolutionNotSupported")
    	case "ResolutionError":
    	logError("ResolutionAcquisitionFailure")
    	case "Reconnecting":
    	let times = message.details["times"].int ?? 0 + 1
    	logError("TryToReconnect (\(times))")
    	case "Reconnected":
    	logTrace("ReconnectSuccess")
    	case "Disconnect":
    	logError("ReconnectFailed")
    	if status == .idle {
    	break
    	}
    	Task {
    	try await stop()
    	}
    	// TODO: If retryOnDisconnection, try to start emulator
    	case "ScreencapFailed":

根因判断

• 直接结论：这是一个 PlayCover/PlayTools 回传竖屏分辨率 + MAA Core / MaaMacGui 连接失败状态处理不完整 叠加出来的真实崩溃问题，不是单纯的“用户分辨率没设好”。
• 证据链：
  1. PlayCover 实际给到 Core 的尺寸是 1080x1920，Core 正常判定为 UnsupportedResolution。
  2. Core 在 ControlScaleProxy 构造失败后虽然返回了 connect failure，但保留了已经初始化的底层 PlayToolsController。
  3. AsstConnected / Assistant::connected() 又只看底层 controller 是否 inited，没有要求 m_scale_proxy 已成功创建，所以 MaaMacGui 被误导为“已连接”。
  4. MaaMacGui 收到 UnsupportedResolution 只记日志，不中断连接/启动流程，于是继续显示“正在运行中……”并开始任务。
  5. 后续第一次点击走到 Controller::click() 时直接解引用空的 m_scale_proxy，因此出现和日志完全吻合的 SIGSEGV。

给用户的建议

• 用户现在可以直接尝试的动作：
  • 暂时不要走 MacPlayTools / PlayCover 直连 这条链路。
  • 优先改用 Compatible / ADB 连接（日志里 localhost:5555 + 1280x720 已证明可以正常进入 Connected 并继续跑任务）。
  • 如果仍想用 PlayCover 直连，先确认 PlayCover 实际输出给外部工具的是横屏 16:9，而不是 UI 看起来横屏、底层却仍是 1080x1920。
• 是否建议升级 / 重下完整包 / 同步资源 / 重置配置：
  • 同步资源不是关键，这不是资源任务定义错误。
  • 可以尝试最新的 PlayCover 链接版本，但从当前代码看，即使 PlayCover 继续回传 1080x1920，MAA 这边仍存在“错误后继续跑任务并崩溃”的缺陷。
• 是否需要等待开发者修复：
  • 需要。 当前 MaaAssistantArknights HEAD 和 MaaMacGui master 都还能看到这条问题链，尚不能认为已修复。
• 是否有临时绕过方案：
  • 有，使用 ADB / Compatible 连接是当前最可行的绕过方案。

修复方案

1. 代码 / 资源 / 配置层修复
   • Core：
     • Controller::connect() 在 screencap() 失败或 ControlScaleProxy 构造失败时，必须 clear_info() 或至少清空 m_controller / m_scale_proxy / m_uuid，不能留下“底层 controller 已连上，但缩放代理不存在”的半初始化状态。
     • Controller::inited() 不应只看 m_controller->inited()；对需要缩放代理的路径，应把 m_scale_proxy != nullptr 也纳入判定。
     • Controller::click() / swipe() 需要像 m_controller 一样对 m_scale_proxy 做判空保护，避免空指针崩溃。
   • MaaMacGui：
     • 不能把 AsstConnected 当成连接成功的充分条件；应等待明确的 Connected / ResolutionInfo 成功回调，或在收到 UnsupportedResolution 后直接抛出连接失败。
     • processConnectionInfo("UnsupportedResolution") 不应只写日志，应该同步终止连接/阻止 Running 与后续 startTasks()。
2. 需要补充的日志或截图
   • 若要进一步确认崩溃栈，最好补 MAA.exe.dmp/macOS crash report 或符号化堆栈；但就当前日志看，根因已经足够清晰。
   • 若要继续追 PlayCover 本身，还需要 PlayCover 实际回传 framebuffer 尺寸/方向的独立证据。
3. 需要补充的测试
   • Core 单测/集成测试：模拟 get_screen_res() 返回 1080x1920，断言 connect 失败后 AsstConnected == false，并且后续 click() 不崩溃。
   • MaaMacGui 测试：注入 UnsupportedResolution 回调后，断言不会记录 Running，也不会进入 status = .busy。

给修复 AI 的建议（可复制）

点击此处展开

现象：
PlayCover / MacPlayTools 返回 1080x1920 竖屏画面时，MAA Core 已发出 UnsupportedResolution，但 MaaMacGui 仍把连接当成功，继续启动任务，并在第一次点击时 SIGSEGV。

关键证据：
- asst.log: ConnectionInfo {"details":{"height":1920,"width":1080},"what":"UnsupportedResolution","why":"Low screen resolution"}
- gui.log: “模拟器分辨率不支持……”之后立刻出现“正在运行中……”和“开始任务：StartUp”
- asst.log: 首次 SubTaskStart ClickSelf（如 GameStart / ReturnButton）后立即 `Signal caught: SIGSEGV (Segmentation Fault)`
- Controller::click() 直接解引用 m_scale_proxy
- Controller::connect() 在 ControlScaleProxy 构造失败时 return false，但没有 clear_info()
- Assistant::connected() / AsstConnected() 只看底层 controller 是否 inited
- MaaMacGui 的 MAAHandle.connect() 只要 AsstConnected 为真就认定 connect 成功
- MaaMacGui 的 processConnectionInfo("UnsupportedResolution") 仅 logError，不中断流程

可能相关线索（待验证）：
1. Core 半初始化状态：m_controller 已存在，但 m_scale_proxy 为空。
2. AsstConnected 语义过宽，导致 GUI 误判“连接成功”。
3. MacGui 应该以 Connected/ResolutionInfo 成功回调为准，UnsupportedResolution 应直接转为 connectFailed。
4. 至少需要给 click/swipe 增加 m_scale_proxy 判空，先消除崩溃。

置信度

• 高
• 还缺什么证据：如果要精确到“崩在 Controller::click 的哪一条指令”，还缺 crash dump / 符号化堆栈；但对 issue 结论本身不是必需的

English translation

Click here to expand

Issue Summary

• Issue: #16448
• Version / resource timestamp: 6.90; the reproduction logs show built-in resource 辟路之人 (2026-04-28 10:04:05) and later external resource 承诺 (2026-05-01 09:02:14)
• Environment / connection / tasks: PlayCover; the user configured 1920 x 1080, but the logs show the failing path is MacPlayTools, mainly while running StartUp and Recruit
• Key user-visible messages: Connecting…, Unsupported emulator resolution..., Running…
• User-visible symptom: PlayCover actually returned a portrait 1080x1920 frame. Core correctly reported UnsupportedResolution, but the GUI still transitioned into running state and started tasks; the first click then triggered SIGSEGV

Key Evidence

• gui.log
  • At 2026-05-01 04:22:34, the GUI logged Connecting…
  • Immediately after that, it logged Unsupported emulator resolution...
  • But the next line was already Running…
  • Then it continued with Start task: StartUp
  • The same sequence repeated multiple times, so this is a stable state-handling bug, not a one-off UI glitch
• asst.log
  • At 12:22:35.024, Core emitted ConnectionInfo {"details":{"height":1920,"width":1080},"what":"UnsupportedResolution","why":"Low screen resolution"}
  • In the same reproduction, Core still started StartUp at 12:22:35.153
  • At 12:22:41.230, right after SubTaskStart for a click action on GameStart, it crashed with Signal caught: SIGSEGV (Segmentation Fault)
  • Later reproductions show the same pattern: UnsupportedResolution first, then task execution, then SIGSEGV on the first click
  • Later logs show that when the user switched to adb localhost:5555 / Compatible, Core reported ResolutionGot 1280x720, Connected, and ResolutionInfo Normal, and tasks could continue, which isolates the problem to the MacPlayTools / PlayCover path rather than resource/task definitions

Root Cause

This is a real bug caused by a chain of failures, not just user misconfiguration:

1. PlayCover / PlayTools returned a portrait 1080x1920 framebuffer.
2. Core correctly rejected it in ControlScaleProxy as UnsupportedResolution.
3. Controller::connect() returned failure when proxy creation failed, but it left the underlying controller alive.
4. AsstConnected / Assistant::connected() only checked whether the low-level controller was initialized, not whether the scale proxy existed.
5. MaaMacGui therefore treated the connection as successful, logged Running, and started tasks.
6. On the first click, Controller::click() dereferenced m_scale_proxy without a null check, leading to SIGSEGV.

Advice for the User

• Do not use the MacPlayTools / PlayCover direct path for now.
• Prefer Compatible / ADB mode as a workaround. The attached logs already show localhost:5555 + Compatible working with 1280x720.
• Updating PlayCover may help the upstream portrait-frame issue, but MAA itself still has a bug here: it should stop cleanly instead of continuing and crashing.
• This issue likely still needs a code fix in both Core and MaaMacGui.

Fix Plan

1. Core
   • Clear controller state when screencap() or ControlScaleProxy initialization fails.
   • Make Controller::inited() require a valid scale proxy on controller types that need it.
   • Add null checks for m_scale_proxy in click() / swipe() to avoid crashes.
2. MaaMacGui
   • Do not treat AsstConnected as sufficient proof of a successful connection.
   • If UnsupportedResolution is received, fail the connection flow immediately and do not log Running or start tasks.
3. Tests
   • Add a regression test where the reported screen resolution is 1080x1920, and verify that:
     • connection fails,
     • AsstConnected == false,
     • subsequent input calls do not crash,
     • the GUI never transitions to running state.

Confidence

• High
• Missing evidence: a symbolized crash stack would help pinpoint the exact crash frame, but it is not required to establish the root cause above

---

点击此处展开分析过程

● skill(maa-issue-log-analysis)

● Get issue details (MCP: github-mcp-server) · owner: "MaaAssistantArknights", repo: "MaaAssistantA…
  └ [{"id":4365707927,"body":"🤖 **MaaBot 正在分析该 Issue...**
    \n\n感谢您的反馈！AI 正在...

● Get issue details (MCP: github-mcp-server) · owner: "MaaAssistantArknights", repo: "MaaAssistantA…
  └ {"number":16448,"title":"MAA 錯誤偵察Playcover
    實際視窗最終閃退","body":"Checkboxes\...

● Get HEAD commit (shell)
  │ git rev-parse HEAD
  └ 2 lines...

先把日志和相关代码一并拉出来看，确认这是“连接状态误判”还是单纯的分辨率不支持。

● Search (glob)
  │ "src/**/*.{swift,mm,m,cs,cpp,h,hpp}"
  └ 10 files found

● Search (grep)
  │ "UnsupportedResolution|ConnectFailed|PlayCover|Win32Controller|AttachWindow|
  │ ConnectionInfo|screencap|click" in *.{cpp,h,hpp,cs,swift,m,mm} (src,
  │ include)
  └ 8 lines found

● Download issue logs (shell)
  │ mkdir -p /tmp/maa16448 && cd /tmp/maa16448 && curl -L --fail -o asst.log
  │ https://github.com/user-attachments/files/27314240/asst.log && curl -L
  │ --fail -o gui.log https://github.com/user-attachments/files/27314239/gui.log
  │ && wc -l asst.log gui.log
  └ 12 lines...

● Search (grep)
  │ "connected|connect|UnsupportedResolution|PlayCover|resolution|screen|click|S
  │ tart|Error|Exception|crash" (/tmp/maa16448/gui.log)
  └ 11 lines found

● Search (grep)
  │ "UnsupportedResolution|ConnectFailed|ConnectionInfo|TaskChainError|SubTaskEr
  │ ror|PlayCover|screencap|click|null|segmentation|crash|fatal"
  │ (/tmp/maa16448/asst.log, /tmp/maa16448/gui.log)
  └ 11 lines found

● Search (grep)
  │ "UnsupportedResolution|AsstConnect|ConnectionInfo|PlayTools|PlayCover|MacGui
  │ |connect.*success|append.*controller|Controller" in
  │ *.{swift,cpp,h,hpp,mm,m,cs} (src)
  └ 100 files found

我已经拿到原始 `asst.log` / `gui.log`。下一步看两条线：一条是日志里的时间线，一条是 PlayCover/MacGui 当前代码里怎么处理 `UnsupportedResolution` 和“已连接”。

● Search (glob)
  │ "src/**/*MacGui*"
  └ No matches found

● Search (glob)
  │ "src/**/*Play*"
  └ 2 files found

● Search (grep)
  │ "PlayCover|PlayTools|UnsupportedResolution|ConnectionInfo|ConnectFailed" in
  │ src/**/*.{swift,mm,m,cpp,h,hpp,cs}
  └ 8 lines found

● Search (grep)
  │ "PlayCover|UnsupportedResolution|Resolution|ConnectFailed|Connected|Connecti
  │ onInfo|正在运行中|正在连接|分辨率不支持|PlayTools" (/tmp/maa16448/asst.log,
  │ /tmp/maa16448/gui.log)
  └ 11 lines found

● Read Assistant.cpp
  │ src/MaaCore/Assistant.cpp
  └ L100:180 (80 lines read)

● Read PlayToolsController.cpp
  │ src/MaaCore/Controller/PlayToolsController.cpp
  └ L1:260 (260 lines read)

● Read AsstMsg.h
  │ src/MaaCore/Common/AsstMsg.h
  └ L1:120 (71 lines read)

● Show key log excerpts (shell)
  │ echo '--- gui excerpts ---' && rg -n -C 4
  │ '正在连接|分辨率不支持|正在运行中|连接' /tmp/maa16448/gui.log | head -n 80
  │ && echo '--- asst excerpts ---' && rg -n -C 4 'UnsupportedResolution|Connect
  │ ionInfo|ConnectFailed|connect|PlayCover|PlayTools|screencap|click'
  │ /tmp/maa16448/asst.log | head -n 200
  └ 5 lines...

● Read PlayToolsController.h
  │ src/MaaCore/Controller/PlayToolsController.h
  └ L1:260 (120 lines read)

● Search (grep)
  │ "what.*UnsupportedResolution|UnsupportedResolution|resolution" in
  │ *.{cpp,h,hpp} (src/MaaCore)
  └ 8 lines found

● Inspect log timeline (shell)
  │ echo '--- gui head/tail ---' && sed -n '1,80p' /tmp/maa16448/gui.log &&
  │ echo '--- gui tail ---' && tail -n 80 /tmp/maa16448/gui.log && echo '---
  │ asst key lines ---' && grep -nE
  │ 'UnsupportedResolution|ConnectionInfo|ConnectFailed|PlayTools|click|screen
  │ cap|Exception|fatal|terminate|Segmentation|SIG' /tmp/maa16448/asst.log | …
  └ 16 lines...

● Read copilot-tool-output-1777795394581-68j65m.txt
  │ /tmp/copilot-tool-output-1777795394581-68j65m.txt
  └ L1:260 (234 lines read)

● Read copilot-tool-output-1777795394581-68j65m.txt
  │ /tmp/copilot-tool-output-1777795394581-68j65m.txt
  └ L261:520 (161 lines read)

● Read copilot-tool-output-1777795393989-vhbhpo.txt
  │ /tmp/copilot-tool-output-1777795393989-vhbhpo.txt
  └ L1:220 (157 lines read)

关键证据已经很明确：`UnsupportedResolution` 之后 GUI 仍然进入“正在运行中”，Core 随后继续跑任务并多次 `SIGSEGV`。我现在把 core 里的连接返回路径和回调语义补齐，确认是哪里把失败当成功了。

● Read ControlScaleProxy.cpp
  │ src/MaaCore/Controller/ControlScaleProxy.cpp
  └ L1:80 (80 lines read)

● Read Controller.cpp
  │ src/MaaCore/Controller/Controller.cpp
  └ L1:140 (140 lines read)

● Search (grep)
  │ "Connected|ResolutionGot|ResolutionInfo|UnsupportedResolution|ConnectionInfo
  │ " in *.{cpp,h,hpp} (src/MaaCore)
  └ 9 lines found

● Search (grep)
  │ "开始任务：|正在运行中|连接失败|模拟器分辨率不支持|截图失败|打开客户端失败"
  │ in **/*.{cs,xaml,swift,m,mm,cpp,h,hpp} (src)
  └ 51 lines found

● Search (grep)
  │ "bool .*connect\(" in *.cpp (src/MaaCore/Controller)
  └ 41 lines found

● Search (grep)
  │ "AsstConnect\(|connected\(|running\(" in *.{cpp,h} (src/MaaCore)
  └ 65 lines found

● Search code (MCP: github-mcp-server) · "PlayCover链接" org:MaaAssistantArknights · query: ""PlayC…
  └ {"total_count":2,"incomplete_results":false,"items":[{"name":"Localizabl...

我还补看了 `MaaMacGui` 上游代码，避免把 GUI 侧误判只靠日志猜。现在确认一下它是否在 `AsstConnect` 失败时仍然切到 running，或者把 `UnsupportedResolution` 当普通提示处理。

● Read Controller.cpp
  │ src/MaaCore/Controller/Controller.cpp
  └ L220:340 (120 lines read)

● Read Assistant.cpp
  │ src/MaaCore/Assistant.cpp
  └ L420:500 (81 lines read)

● Get file or directory contents (MCP: github-mcp-server) · MeoAsstMac/Model/MAAViewModel.swift · o…
  └ Output too large to read at once (22.2 KB). Saved to: /tmp/1777795426280...

● Get file or directory contents (MCP: github-mcp-server) · Resources/Localizable.xcstrings · owner…
  └ Output too large to read at once (113.5 KB). Saved to: /tmp/177779542630...

● Search (grep)
  │ "AsstConnect|ConnectionInfo|UnsupportedResolution|ResolutionNotSupported|Scr
  │ eencapFailed|status = \.pending|status = \.idle|status =
  │ \.busy|startTasks|正在运行中|ConnectFailed"
  │ (/tmp/1777795426280-copilot-tool-output-0p2r0w.txt)
  └ 160 lines found

● Search (grep)
  │ "PlayCover链接|ResolutionNotSupported|连接失败|正在连接|正在运行中|截图失败|
  │ 打开客户端失败" (/tmp/1777795426307-copilot-tool-output-enzknu.txt)
  └ 41 lines found

● Read AsstCaller.cpp
  │ src/MaaCore/AsstCaller.cpp
  └ L100:160 (60 lines read)

● Search (grep)
  │ "ResolutionNotSupported|UnsupportedResolution|ScreencapFailed|ConnectionInfo
  │ |ConnectFailed|CheckSettings|handleEarlyReturn"
  │ (/tmp/1777795426280-copilot-tool-output-0p2r0w.txt)
  └ 124 lines found

● Read 1777795426280-copilot-tool-output-0p2r0w.txt
  │ /tmp/1777795426280-copilot-tool-output-0p2r0w.txt
  └ L208:260 (52 lines read)

● Read 1777795426280-copilot-tool-output-0p2r0w.txt
  │ /tmp/1777795426280-copilot-tool-output-0p2r0w.txt
  └ L435:490 (56 lines read)

● List commits (MCP: github-mcp-server) · owner: "MaaAssistantArknights", repo: "MaaMacGui", sha: "…
  └ [{"sha":"7eed4830027010efb4f8218b1f29ad51dc77d3d4","html_url":"https://g...

● Search code (MCP: github-mcp-server) · repo:MaaAssistantArknights/MaaMacGui "AsstConnect(" · quer…
  └ {"total_count":0,"incomplete_results":false}

● Search code (MCP: github-mcp-server) · repo:MaaAssistantArknights/MaaMacGui "func connect(adbPath…
  └ {"total_count":1,"incomplete_results":false,"items":[{"name":"Maa.swift"...

● Search code (MCP: github-mcp-server) · repo:MaaAssistantArknights/MaaMacGui "UnsupportedResolutio…
  └ {"total_count":1,"incomplete_results":false,"items":[{"name":"MaaMessage...

● Get file or directory contents (MCP: github-mcp-server) · MeoAsstMac/Core/Maa.swift · owner: "Maa…
  └ successfully downloaded text file (SHA: 94f0780c5a8a34b8ad44c702d7749e16...

● Get file or directory contents (MCP: github-mcp-server) · MeoAsstMac/Core/MaaMessage.swift · owne…
  └ successfully downloaded text file (SHA: 07dba027e18f09d0535d73f8c5e2e307...

● Search (grep)
  │ "AsstAsyncConnect|async_connect\(|AsyncConnect" in *.{cpp,h} (src/MaaCore)
  └ 36 lines found

● Search (grep)
  │ "connected\(\) const|return inited\(|inited\(\) const" in *.{cpp,h,hpp}
  │ (src/MaaCore)
  └ 103 lines found

● Search (grep)
  │ "append_async_call\(|AsyncCallItem::Type::Connect|ctrl_connect\("
  │ (src/MaaCore/Assistant.cpp)
  └ 66 lines found

● Read Assistant.cpp
  │ src/MaaCore/Assistant.cpp
  └ L340:420 (81 lines read)

● Search (grep)
  │ "Signal caught:
  │ SIGSEGV|StartButton2|ProcessTask|StartGameTask|ScreencapFailed"
  │ (/tmp/maa16448/asst.log)
  └ 9 lines found

● Read Assistant.cpp
  │ src/MaaCore/Assistant.cpp
  └ L181:260 (80 lines read)

● Read Assistant.cpp
  │ src/MaaCore/Assistant.cpp
  └ L580:680 (101 lines read)

● Extract decisive asst lines (shell)
  │ grep -nE 'UnsupportedResolution|Signal caught: SIGSEGV|get_image screencap
  │ failed|ScreencapFailed|StartGame is not supported on PlayTools|start
  │ game|ProcessTask|SubTaskError|TaskChainError' /tmp/maa16448/asst.log | head
  │ -n 120
  └ 9 lines...

● Read copilot-tool-output-1777795468062-lu9ued.txt
  └ /tmp/copilot-tool-output-1777795468062-lu9ued.txt

● Read copilot-tool-output-1777795468062-lu9ued.txt
  │ /tmp/copilot-tool-output-1777795468062-lu9ued.txt
  └ L1:180 (50 lines read)

● Read Controller.cpp
  │ src/MaaCore/Controller/Controller.cpp
  └ L140:220 (81 lines read)

● Read Assistant.h
  │ src/MaaCore/Assistant.h
  └ L140:220 (81 lines read)

● Search (grep)
  │ "m_ctrler\s*=|std::make_shared<Controller>|Controller m_ctrler|m_ctrler->"
  │ (src/MaaCore/Assistant.cpp, src/MaaCore/Assistant.h)
  └ 117 lines found

● Read Controller.h
  │ src/MaaCore/Controller/Controller.h
  └ L1:120 (120 lines read)

● Search (grep)
  │ "bool asst::Controller::inited\(\) const"
  │ (src/MaaCore/Controller/Controller.cpp)
  └ No matches found

● Search code (MCP: github-mcp-server) · repo:MaaAssistantArknights/MaaMacGui "connectFailed" "MaaC…
  └ {"total_count":1,"incomplete_results":false,"items":[{"name":"Maa.swift"...

● Search (grep)
  │ "ResolutionNotSupported" (/tmp/1777795426307-copilot-tool-output-enzknu.txt)
  └ 13 lines found

● Search (grep)
  │ "Controller::inited" (src/MaaCore/Controller/Controller.cpp)
  └ 7 lines found

● Search (grep)
  │ "TouchModeNotAvaiable|CheckSettings|Running|ConnectingToEmulator"
  │ (/tmp/1777795426307-copilot-tool-output-enzknu.txt)
  └ 23 lines found

证据链已经闭环了：不是单一“分辨率不支持”，而是 `UnsupportedResolution` 之后连接状态没有被真正判失败，随后第一次点击直接踩空指针。最后我把外链行号补齐后就写结论文件。

● Get local code line numbers (shell)
  │ echo '--- local core line numbers ---' && nl -ba
  │ src/MaaCore/Controller/ControlScaleProxy.cpp | sed -n '15,42p' && echo
  │ '--- Controller connect/click ---' && nl -ba
  │ src/MaaCore/Controller/Controller.cpp | sed -n
  │ '156,165p;222,275p;347,350p' && echo '--- Assistant connect/connected ---'…
  └ 127 lines...

● Get MaaMacGui line numbers (shell)
  │ mkdir -p /tmp/maa16448/code && curl -L --fail -o
  │ /tmp/maa16448/code/Maa.swift
  │ https://raw.githubusercontent.com/MaaAssistantArknights/MaaMacGui/7eed4830
  │ 027010efb4f8218b1f29ad51dc77d3d4/MeoAsstMac/Core/Maa.swift && curl -L
  │ --fail -o /tmp/maa16448/code/MAAViewModel.swift …
  └ 187 lines...

● Search (grep)
  │ ""ResolutionNotSupported"\s*:\s*\{|"Running"\s*:\s*\{|"ConnectingToEmulator"
  │ \s*:\s*\{|"CheckSettings"\s*:\s*\{|"ConnectFailed"\s*:\s*\{"
  │ (/tmp/1777795426307-copilot-tool-output-enzknu.txt)
  └ 5 lines found

● Get Maa.swift connected lines (shell)
  │ echo '--- Maa.swift connected ---' && nl -ba /tmp/maa16448/code/Maa.swift |
  │ sed -n '96,112p'
  └ 19 lines...

● Get Maa.swift property lines (shell)
  │ nl -ba /tmp/maa16448/code/Maa.swift | sed -n '112,126p'
  └ 16 lines...

● Edit
  └ Create copilot_answer.md

● Read copilot_answer.md
  └ L1:260 (179 lines read)

● Read copilot_answer.md

已完成分析，最终结论已写入 `copilot_answer.md`。

结论是：`#16448` 的根因不是单纯“PlayCover 分辨率不支持”，而是 **PlayCover/MacPlayTools 回传了 `1080x1920` 竖屏画面，Core 发出 `UnsupportedResolution` 后仍留下半初始化连接状态，MaaMacGui 又把这次失败误判成连接成功，最终在第一次点击时空指针崩溃**。文档里已经整理了关键日志、当前代码依据、临时绕过方案（优先改用 `Compatible` / ADB），以及对 Core 与 `MaaMacGui` 的具体修复建议。


Changes   +180 -0
Requests  1 Premium (4m 43s)
Tokens    ↑ 2.4m • ↓ 15.8k • 2.2m (cached) • 5.5k (reasoning)

🔗 GitHub Action 运行记录

[Georgechengtai]

如果能多口問一句的話，能知道Mac版MAA真的有導出日志，一鍵複製版本這些功能嗎

[Saratoga-Official]

mac版那边的开发者不常看issue，问题和建议可以加mac版maa的群问
1091086083

[github-actions]

This issue has been inactive for a prolonged period and will be closed automatically in 7 days.
该问题已长时间处于闲置状态，7 天后将自动关闭。