在windows10和windows11两台电脑上面分别安装openhuman V0.54都不能正常打开

[GHYgwx]

Use a concise sentence-case title that describes the broken behavior. Do not add Bug or bracket prefixes to the title.

Summary

在windows10和windows11两台电脑上面分别安装openhuman V0.54都不能正常打开

Problem

一、在dell inspiron 14 7460，windows 10系统上安装openhuman V0.54，安装完毕，在该软件的欢迎界面里面，分别选择google和Twitter两个登录方式，在网页验证完毕，出现如下图片，点击“Openhuman”按钮，始终不能转回Openhuman软件欢迎界面：

二、在联想Y7000拯救者，Windows11，也是一样的情况。

What happened vs what you expected, impact, and steps to reproduce (ordered, minimal). Include version / platform (app version, OS, desktop vs dev) if known.

Solution (optional)

Suspected cause, workaround, or proposed fix. Skip if unknown.

Acceptance criteria

• Repro gone — Bug no longer reproduces on the stated environment (or root cause documented if intentional).
• Regression safety — Unit, integration, or E2E coverage added or updated if this should not come back.
• Diff coverage ≥ 80% — the fix PR meets the changed-lines coverage gate (Vitest + cargo-llvm-cov, enforced by .github/workflows/coverage.yml).
• … — Other verify-before-close items.

Related

Links to issues, PRs, logs, or prior discussion.

[17600420419]

After I completed the installation, I also encountered a problem where I couldn't return after the authorization was completed.

[lmliheng]

我也是

[burninghe]

I encountered the same problem, after completing the webpage authentication, I couldn't redirect to the application section normally. I don't know where to store the relevant debug logs. If possible, I am willing to provide more assistance. By the way, the system is Windows 10。

[Giftia]

Same issue

[iverson-fa]

I encountered the same problem.

[sunilkumarvalmiki]

我对照了一下这个现象和当前公开 release 状态。

结论：这看起来和 #2521 是同一类问题，主要是 公开的 Windows v0.54.0 安装包落后于 main 上已经合并的 OAuth 修复，不是当前 main 上的新代码回归。

已确认的信息：

• 最新公开 release 仍是 v0.54.0，发布时间是 2026-05-19，target commit 是 c25fc8e5fd3e7716f416571cd53b34247c94ddbe。
• Windows OAuth 回调相关修复在这个 release 之后才合并：fix(tauri): forward Windows local-runtime OAuth callbacks #2469、feat(auth): loopback OAuth redirect with deep-link fallback #2511，后续还有 fix(oauth): make loopback redirect actually work, plus settings cleanup #2550 相关补强。
• 所以重新安装当前官网/Release 页面里的 v0.54.0 Windows 安装包，仍然可能出现网页登录成功后回不到 OpenHuman 欢迎页的问题。

建议这里先按 release packaging gap 处理：需要官方发布一个包含 #2469 / #2511 / #2550 之后 commit 的新 Windows 安装包。当前没有必要再开一个重复代码 PR；要验证修复，需要用 main 之后的 Windows 构建或下一版官方 release。

[YellowSnnowmann]

Verified that all three OAuth redirect fixes are merged and present on main:

PR	Title	Merged
#2469	fix(tauri): forward Windows local-runtime OAuth callbacks	May 22
#2511	feat(auth): loopback OAuth redirect with deep-link fallback	May 23
#2550	fix(oauth): make loopback redirect actually work, plus settings cleanup	May 23

The v0.54.0 installer was built from commit c25fc8e5 (May 19) — before any of these fixes landed. The current main has a two-layer solution:

1. Loopback OAuth server — spins up a one-shot HTTP server on 127.0.0.1:53824 so the browser redirect never touches the OS deep-link mechanism (the root cause of the Windows failure).
2. Windows named-pipe IPC — safety-net forwarding via \\.\pipe\com.openhuman.app-deeplink if the loopback path is unavailable.

No new code changes are required. This will be resolved by the next release build that includes these commits. Closing as a release packaging gap per @sunilkumarvalmiki's analysis.