[BUG] 初始化NapCat失败 fetchServices Timeout!

minecraft4668 commented 3 weeks ago

系统版本

Windows Server 2022

QQNT 版本

9.9.15-28060

NapCat 版本

2.6.14

OneBot 客户端

/

发生了什么?

初始化NapCat失败 fetchServices Timeout!

如何复现

使用NapCat.FrameWork出现错误，按照llqqnt官方修补后仍然出现错误。

期望的结果?

正常启动QQ

NapCat 运行日志

[LiteLoader] Found Plugin: 彻底禁用更新
[LiteLoader] Found Plugin: 插件列表查看
[LiteLoader] Found Plugin: LLOneBot
[LiteLoader] Found Plugin: NapCatQQ
[NapCat] [Info] 开始初始化NapCat
Error occurred in handler for 'get-remote-win': Error: No handler registered for 'get-remote-win'
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:82968)
    at WebContents.emit (node:events:519:28)
(node:15760) UnhandledPromiseRejectionWarning: Error: node-loader:
RangeError: Maximum call stack size exceeded
    at 15797 (C:\Program Files\Tencent\QQNT\versions\9.9.15-28060\resources\app\application\790.background.js)
    at s (C:\Program Files\Tencent\QQNT\versions\9.9.15-28060\resources\app\application\background.js)
    at 16232 (C:\Program Files\Tencent\QQNT\versions\9.9.15-28060\resources\app\application\790.background.js)
    at s (C:\Program Files\Tencent\QQNT\versions\9.9.15-28060\resources\app\application\background.js)
    at o (C:\Program Files\Tencent\QQNT\versions\9.9.15-28060\resources\app\application\790.background.js)
    at get session (C:\Program Files\Tencent\QQNT\versions\9.9.15-28060\resources\app\application\790.background.js)
    at get ntSession (C:\Program Files\Tencent\QQNT\versions\9.9.15-28060\resources\app\application\790.background.js)
    at 25884 (C:\Program Files\Tencent\QQNT\versions\9.9.15-28060\resources\app\application\790.background.js)
    at s (C:\Program Files\Tencent\QQNT\versions\9.9.15-28060\resources\app\application\background.js)
    at 92103 (C:\Program Files\Tencent\QQNT\versions\9.9.15-28060\resources\app\application\790.background.js)
(Use `QQ --trace-warnings ...` to show where the warning was created)
(node:15760) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
[NapCat] [Error] 初始化NapCat失败 fetchServices Timeout!