https://github.com/mamoe/mirai/issues/2882
Mirai版本：2.14.0-RC
mirai-api-http版本：v2.9.1
MCL Addon版本：v2.0.2
iTXTech MCL Version: 2.0.1-b5303b5
protocol: IPAD
heartbeatStrategy: STAT_HB
无签名，通过密码自动登录，无验证码

一直通过WebSocket API正常使用，业务端有一项功能是末位淘汰，逻辑是由新人入群事件触发检查，群员人数超指定人数则踢一位最长时间未发言成员，设定为1995人，稳定运行多年，最近几天发现群人数越来越少了，一直到1967人了都仍然在触发末位淘汰，调试触发memberList接口获取群员列表以更新业务逻辑的成员缓存，由mirai返回的群员列表依然为1995个成员，于是尝试重启mirai，重启后mirai返回的群员列表为1967个成员。
倒查日志发现，无论是业务端的log，还是mirai的log，均显示最后一次接收到退群事件（MemberLeaveEvent.Quit）在2025-05-26 01:39:46，在此以后再也没有接收到任何退群事件。
我运行的bot管理着很多的两、三千人大群，所以可以认为是2025-05-26开始不再能接收到退群事件，目前个人推测可能是Mirai也对群员列表有缓存，Mirai核心收不到退群事件，所以Mirai在重启前返回的群员列表中没有删除退群成员。
与之相对的，在2025-05-26开始，mirai log开始频繁出现下面的报错，在测试群中测试了退群也一样会触发下面的报错：

2025-06-14 20:39:01 E/Bot.[QQ号]: Exception on parsing packet. java.lang.IllegalStateException: Exception in net.mamoe.mirai.internal.network.notice.group.GroupOrMemberListNoticeProcessor@7956774f while processing packet PbMsgInfo. at net.mamoe.mirai.internal.network.components.NoticeProcessorPipelineImpl.handleExceptionInProcess(NoticeProcessorPipeline.kt:105) at net.mamoe.mirai.internal.network.components.NoticeProcessorPipelineImpl.handleExceptionInProcess(NoticeProcessorPipeline.kt:80) at net.mamoe.mirai.internal.pipeline.AbstractProcessorPipeline.process$suspendImpl(ProcessorPipeline.kt:289) at net.mamoe.mirai.internal.pipeline.AbstractProcessorPipeline.process(ProcessorPipeline.kt) at net.mamoe.mirai.internal.pipeline.AbstractProcessorPipeline.process$suspendImpl(ProcessorPipeline.kt:275) at net.mamoe.mirai.internal.pipeline.AbstractProcessorPipeline.process(ProcessorPipeline.kt) at net.mamoe.mirai.internal.network.protocol.packet.chat.receive.OnlinePushPbPushTransMsg.decode(OnlinePush.PbPushTransMsg.kt:45) at net.mamoe.mirai.internal.network.components.PacketCodecImpl.processBody(PacketCodec.kt:492) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline.processBody(CommonNetworkHandler.kt:157) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline.access$processBody(CommonNetworkHandler.kt:102) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline$1$3$1.invokeSuspend(CommonNetworkHandler.kt:126) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline$1$3$1.invoke(CommonNetworkHandler.kt) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline$1$3$1.invoke(CommonNetworkHandler.kt) at kotlinx.coroutines.intrinsics.UndispatchedKt.startCoroutineUndispatched(Undispatched.kt:55) at kotlinx.coroutines.CoroutineStart.invoke(CoroutineStart.kt:112) at kotlinx.coroutines.AbstractCoroutine.start(AbstractCoroutine.kt:126) at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch(Builders.common.kt:56) at kotlinx.coroutines.BuildersKt.launch(Unknown Source) at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch$default(Builders.common.kt:47) at kotlinx.coroutines.BuildersKt.launch$default(Unknown Source) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline$1.invokeSuspend(CommonNetworkHandler.kt:126) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.base/java.lang.Thread.run(Thread.java:833) Caused by: java.io.EOFException: Premature end of stream: expected 4 bytes at net.mamoe.mirai.internal.deps.io.ktor.utils.io.core.StringsKt.prematureEndOfStream(Strings.kt:453) at net.mamoe.mirai.internal.deps.io.ktor.utils.io.core.InputPrimitivesKt.readIntFallback(InputPrimitives.kt:86) at net.mamoe.mirai.internal.deps.io.ktor.utils.io.core.InputPrimitivesKt.readInt(InputPrimitives.kt:17) at net.mamoe.mirai.internal.network.notice.group.GroupOrMemberListNoticeProcessor.processImpl(GroupOrMemberListNoticeProcessor.kt:673) at net.mamoe.mirai.internal.network.components.MixedNoticeProcessor.processImpl(NoticeProcessorPipeline.kt:166) at net.mamoe.mirai.internal.network.components.SimpleNoticeProcessor.process(NoticeProcessorPipeline.kt:147) at net.mamoe.mirai.internal.network.components.SimpleNoticeProcessor.process(NoticeProcessorPipeline.kt:141) at net.mamoe.mirai.internal.pipeline.AbstractProcessorPipeline.process$suspendImpl(ProcessorPipeline.kt:287) ... 27 more WGzeyu created this issue in mamoe/mirai open 2025年05月26日开始无法接收成员退群事件 #2882

https://github.com/mamoe/mirai/issues/2883
Mirai版本：2.14.0-RC
mirai-api-http版本：v2.9.1
MCL Addon版本：v2.0.2
iTXTech MCL Version: 2.0.1-b5303b5
protocol: IPAD
heartbeatStrategy: STAT_HB
无签名，通过密码自动登录，无验证码

一直通过WebSocket API调用，业务端有一项功能是末位淘汰，在出现 #2882 (26日开始无法接收成员退群事件) 的问题之后，由于业务逻辑中也有一份成员列表缓存，本就有定期刷新成员列表的逻辑，于是尝试将原先调用的memberList接口换成latestMemberList接口，结果发现末位淘汰前的排名前列通知功能全重新通知了一遍，说明整个列表排名全部变了，检查获取到的数据发现返回数据中所有成员的lastSpeakTimestamp都完全与joinTimestamp相同，实为joinTimestamp。

复现

zyjson版本：2.5
调用方法：

创建消息基础 (当前消息, 真) 添加获取群员列表 (当前消息, 群号, 真) ' 在这里置入获取指令 当前echo ＝ 添加echo等待队列 (全局echo队列, 当前消息, 3, 18000, 群号) 发送WebSocket (当前连接ID, 编码_Ansi到Utf8 (当前消息.到文本 ())) 从echo队列等待echo出现 (全局echo队列, 当前echo, 100, 20000)

相关代码：

.子程序 添加获取群员列表 .参数 输入json, zyJsonValue, 参考 .参数 目标群, 长整数型 .参数 禁用缓存, 逻辑型 .如果 (禁用缓存) 输入json.置文本 (“command”, “latestMemberList”) 输入json.置长整数 (“content.memberIds[0]”, 0) 输入json.移除成员 (“content.memberIds”, 0) .否则 输入json.置文本 (“command”, “memberList”) .如果结束 输入json.置长整数 (“content.target”, 目标群)

返回数据截取（已脱敏并格式化）：

{ "id": [QQ1], "memberName": "[昵称1]", "specialTitle": "", "permission": "MEMBER", "joinTimestamp": 1744682346, "lastSpeakTimestamp": 1744682346, "muteTimeRemaining": 0, "group": { "id": [群号], "name": "[群名]", "permission": "ADMINISTRATOR" } }, { "id": [QQ2], "memberName": "[昵称2]", "specialTitle": "", "permission": "MEMBER", "joinTimestamp": 1739181298, "lastSpeakTimestamp": 1739181298, "muteTimeRemaining": 0, "group": { "id": [群号], "name": "[群名]", "permission": "ADMINISTRATOR" } }, { "id": [QQ3], "memberName": "[昵称3]", "specialTitle": "", "permission": "MEMBER", "joinTimestamp": 1741005585, "lastSpeakTimestamp": 1741005585, "muteTimeRemaining": 0, "group": { "id": [群号], "name": "[群名]", "permission": "ADMINISTRATOR" } } 网络日志 2025-06-14 21:52:49 V/Net [QQ号]: Send: friendlist.GetTroopMemberListReq(friendlist.GetTroopMemberListReq) 2025-06-14 21:52:50 V/Net [QQ号]: Recv: friendlist.GetTroopMemberListReq 2025-06-14 21:52:50 V/Net [QQ号]: Send: friendlist.GetTroopMemberListReq(friendlist.GetTroopMemberListReq) 2025-06-14 21:52:50 V/Net [QQ号]: Recv: friendlist.GetTroopMemberListReq 2025-06-14 21:52:50 V/Net [QQ号]: Send: friendlist.GetTroopMemberListReq(friendlist.GetTroopMemberListReq) 2025-06-14 21:52:50 V/Net [QQ号]: Recv: friendlist.GetTroopMemberListReq 2025-06-14 21:52:50 V/Net [QQ号]: Send: friendlist.GetTroopMemberListReq(friendlist.GetTroopMemberListReq) 2025-06-14 21:52:50 V/Net [QQ号]: Recv: friendlist.GetTroopMemberListReq 2025-06-14 21:52:50 V/Net [QQ号]: Send: friendlist.GetTroopMemberListReq(friendlist.GetTroopMemberListReq) 2025-06-14 21:52:50 V/Net [QQ号]: Recv: friendlist.GetTroopMemberListReq 2025-06-14 21:52:50 V/Net [QQ号]: Send: friendlist.GetTroopMemberListReq(friendlist.GetTroopMemberListReq) 2025-06-14 21:52:51 V/Net [QQ号]: Recv: friendlist.GetTroopMemberListReq 2025-06-14 21:52:51 V/Net [QQ号]: Send: friendlist.GetTroopMemberListReq(friendlist.GetTroopMemberListReq) 2025-06-14 21:52:51 V/Net [QQ号]: Recv: friendlist.GetTroopMemberListReq 2025-06-14 21:52:51 V/Net [QQ号]: Send: friendlist.GetTroopMemberListReq(friendlist.GetTroopMemberListReq) 2025-06-14 21:52:51 V/Net [QQ号]: Recv: friendlist.GetTroopMemberListReq WGzeyu created this issue in mamoe/mirai open 使用latestMemberList获取到的数据有误，所有成员的最后发言时间内容实为加群时间 #2883

Bot bot = BotFactory.INSTANCE.newBot(1474855171, password, new BotConfiguration() {{ // 配置，例如： fileBasedDeviceInfo(); }});

这一行代码报错
Exception in thread "main" java.lang.NoClassDefFoundError: kotlin/coroutines/EmptyCoroutineContext
at net.mamoe.mirai.utils.BotConfiguration.<init>(BotConfiguration.kt:64)
at net.mamoe.mirai.utils.BotConfiguration.<clinit>(BotConfiguration.kt:550)
at com.tugos.dst.admin.controller.MiraiBotExample.main(MiraiBotExample.java:16)
Caused by: java.lang.ClassNotFoundException: kotlin.coroutines.EmptyCoroutineContext
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
... 3 more

pom文件

<dependency> <groupId>net.mamoe</groupId> <artifactId>mirai-core-jvm</artifactId> <version>2.16.0</version> </dependency> <dependency> <groupId>org.jetbrains.kotlin</groupId> <artifactId>kotlin-stdlib-jdk8</artifactId> <version>1.9.0</version> </dependency>

java版本1.8

我是用mirai-api-http插件，python调用websocket，在长时间运行后总是出现消息发不出去的情况。看log接收信息是正常的，报500发送的信息发不出去，log上也不显示，这是响应

{ "syncId": "***", "data": { "code": 500, "msg": "" } }

重新打开一下Mirai就会恢复正常，只会在较长时间运行（几个小时）后会出现，且不会自动恢复。有无什么解释或者解决方法，万分感谢。

登陆bot的时候报错

E/main: Exception in coroutine Bot ***.MessageSvcSyncerImpl java.lang.IllegalStateException: timeout syncing friend message history. at net.mamoe.mirai.internal.network.components.MessageSvcSyncerImpl.syncMessageSvc(MessageSvcSyncer.kt:68) at net.mamoe.mirai.internal.network.components.MessageSvcSyncerImpl.access$syncMessageSvc(MessageSvcSyncer.kt:35) at net.mamoe.mirai.internal.network.components.MessageSvcSyncerImpl$syncMessageSvc$1.invokeSuspend(MessageSvcSyncer.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)

虽然显示登陆成功，但是bot会被直接关闭

2025-01-21 21:19:48 I/Bot.***: Bot cancelled: Bot closed 2025-01-21 21:19:48 I/Bot.***: Bot login successful. (***) Login successful

如何解决这个问题

没有碰过其他插件的文件，突然显示我的插件错误了
QQ20250119-021203.png QQ20250119-021211.png

似乎是这个包导致的问题
mirai在更新的时候一直报错跑不起来
版本2.14->2.16
$9{TT81MSB@0H{C(I5QT4KO.png

mirai版本

[20:57:19 INFO]: [MiraiMC] Disabling MiraiMC v1.9-pre3 [20:57:19 INFO]: [MiraiMC] Preparing MiraiMC unload. [20:57:19 INFO]: [MiraiMC] Closing all bots [20:57:19 INFO]: [MiraiMC] Stopping bot event listener. [20:57:19 INFO]: [MiraiMC] Closing database. [20:57:29 INFO]: [MiraiMC] ========== [ MiraiMC 公告版 ] ========== [20:57:29 INFO]: [MiraiMC] 1.9-pre2 已发布，即将为非官方mirai核心提供支持 [20:57:29 INFO]: [MiraiMC] 如果你对 Onebot 感兴趣，欢迎尝试对接第三方 mirai 核心 Overflow： [20:57:29 INFO]: [MiraiMC] https://github.com/DreamVoid/MiraiMCAddon-Overflow/releases/tag/v1.0 [20:57:29 INFO]: [MiraiMC] =======================================

扫码登陆（ANDROID_WATCH）
登录不上
以下为日志

> mirai login 2495350235 QRCode ANDROID_WATCH [21:00:36 INFO]: [MiraiMC] 登录新的机器人账号: 2495350235, 协议: ANDROID_WATCH [21:00:36 INFO]: [MiraiMC] EncryptService SPI is not provided, sso secure ecdh will not be initialized. [21:00:36 INFO]: [MiraiMC] ECDH key is invalid, start to fetch ecdh public key from server. [21:00:36 INFO]: [MiraiMC] Successfully fetched ecdh public key from server. [21:00:36 WARN]: [MiraiMC] 当前登录的QQ（2495350235）的登录二维码已准备好 [21:00:36 WARN]: [MiraiMC] 请找到下面的文件并使用登录当前QQ的客户端识别二维码 [21:00:36 WARN]: [MiraiMC] plugins\MiraiMC\qrcode-image\2495350235.png [21:00:36 WARN]: [MiraiMC] 识别完成后，请在客户端完成验证流程 [21:00:36 WARN]: [MiraiMC] 如需取消登录，请输入指令 /miraiverify cancel 2495350235，5秒内将会取消登录 [21:00:36 WARN]: [MiraiMC] 如需帮助，请参阅: https://docs.miraimc.dreamvoid.me/troubleshoot/verify-guide#qrcode [21:00:36 INFO]: [MiraiMC] 已尝试使用系统方式直接打开二维码图片 [21:00:36 INFO]: [MiraiMC] 当前登录的QQ（2495350235）的二维码状态已更新：WAITING_FOR_SCAN [21:00:46 INFO]: [MiraiMC] 当前登录的QQ（2495350235）的二维码状态已更新：WAITING_FOR_CONFIRM [21:00:51 INFO]: [MiraiMC] 当前登录的QQ（2495350235）的二维码状态已更新：CONFIRMED [21:00:51 WARN]: [MiraiMC] Failed with auth method: QRCode net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(2495350235), code=45, title=禁止登录, message=你当前使用的QQ版本过低，请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:490) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) ~[mirai-core-all-2.16.0-all.jar:2.16.0] [21:00:51 WARN]: [MiraiMC] Exception in resumeConnection. net.mamoe.mirai.internal.network.handler.selector.SelectorRequireReconnectException: null [21:00:51 INFO]: [MiraiMC] ECDH key is valid. [21:00:51 WARN]: [MiraiMC] Failed with auth method: Error[net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(2495350235), code=45, title=禁止登录, message=你当前使用的QQ版本过低，请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=)]@1911529865 net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byQRCode()) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:263) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:247) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) ~[mirai-core-all-2.16.0-all.jar:2.16.0] Suppressed: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(2495350235), code=45, title=禁止登录, message=你当前使用的QQ版本过低，请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:490) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) ~[mirai-core-all-2.16.0-all.jar:2.16.0] Caused by: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(2495350235), code=45, title=禁止登录, message=你当前使用的QQ版本过低，请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:490) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ~[mirai-core-all-2.16.0-all.jar:2.16.0] ... 5 more [21:00:51 WARN]: [MiraiMC] Exception in resumeConnection. net.mamoe.mirai.internal.network.components.LoginFailedExceptionAsNetworkException: BotAuthorization(BotAuthorization.byQRCode()) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:249) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) ~[mirai-core-all-2.16.0-all.jar:2.16.0] Suppressed: net.mamoe.mirai.internal.network.handler.selector.SelectorRequireReconnectException Caused by: net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byQRCode()) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:263) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:247) ~[mirai-core-all-2.16.0-all.jar:2.16.0] ... 6 more Suppressed: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(2495350235), code=45, title=禁止登录, message=你当前使用的QQ版本过低，请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:490) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) ~[mirai-core-all-2.16.0-all.jar:2.16.0] Caused by: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(2495350235), code=45, title=禁止登录, message=你当前使用的QQ版本过低，请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:490) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) ~[mirai-core-all-2.16.0-all.jar:2.16.0] at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ~[mirai-core-all-2.16.0-all.jar:2.16.0] ... 5 more [21:00:51 WARN]: [MiraiMC] Network selector received exception, closing bot. (net.mamoe.mirai.internal.network.components.LoginFailedExceptionAsNetworkException: BotAuthorization(BotAuthorization.byQRCode()) threw an exception during authorization process. See cause below.) [21:00:51 WARN]: [MiraiMC] 登录机器人时出现异常，原因: BotAuthorization(BotAuthorization.byQRCode()) threw an exception during authorization process. See cause below. [21:00:51 INFO]: [MiraiMC] Bot cancelled: Bot closed

2021-11-23 15:37:14 E/Bot.BotID: Exception on parsing packet. java.lang.IllegalStateException: Exception in net.mamoe.mirai.internal.network.notice.priv.PrivateMessageProcessor@2626c626 while processing packet Msg. at net.mamoe.mirai.internal.network.components.NoticeProcessorPipelineImpl.process$suspendImpl(NoticeProcessorPipeline.kt:241) at net.mamoe.mirai.internal.network.components.NoticeProcessorPipelineImpl$process$1.invokeSuspend(NoticeProcessorPipeline.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:194) at io.ktor.util.pipeline.SuspendFunctionGun.access$resumeRootWith(SuspendFunctionGun.kt:15) at io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:89) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:194) at io.ktor.util.pipeline.SuspendFunctionGun.access$resumeRootWith(SuspendFunctionGun.kt:15) at io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:89) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:194) at io.ktor.util.pipeline.SuspendFunctionGun.access$resumeRootWith(SuspendFunctionGun.kt:15) at io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:89) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:194) at io.ktor.util.pipeline.SuspendFunctionGun.access$resumeRootWith(SuspendFunctionGun.kt:15) at io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:89) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.base/java.lang.Thread.run(Thread.java:833) Caused by: java.lang.IllegalStateException: Failed to download forward message `yk0BVERsQYR9PjpTNGYi3kH/B/+sZLPmbKIkBqIBfz7Aj8ce7n0CXBG3LcA5ARry` at net.mamoe.mirai.internal.MiraiImpl.downloadForwardMessage$suspendImpl(MiraiImpl.kt:843) at net.mamoe.mirai.internal.MiraiImpl$downloadForwardMessage$1.invokeSuspend(MiraiImpl.kt) ... 25 more Caused by: java.lang.IllegalStateException: Cannot download forward message at net.mamoe.mirai.internal.MiraiImpl.downloadMultiMsgTransmit(MiraiImpl.kt:1221) at net.mamoe.mirai.internal.MiraiImpl.access$downloadMultiMsgTransmit(MiraiImpl.kt:71) at net.mamoe.mirai.internal.MiraiImpl$downloadMultiMsgTransmit$1.invokeSuspend(MiraiImpl.kt) ... 25 more Caused by: java.net.UnknownHostException: ssl.htdata.qq.com at java.base/java.net.InetAddress$CachedAddresses.get(InetAddress.java:801) at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1509) at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1367) at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1301) at okhttp3.Dns$Companion$DnsSystem.lookup(Dns.kt:49) at okhttp3.internal.connection.RouteSelector.resetNextInetSocketAddress(RouteSelector.kt:164) at okhttp3.internal.connection.RouteSelector.nextProxy(RouteSelector.kt:129) at okhttp3.internal.connection.RouteSelector.next(RouteSelector.kt:71) at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:213) at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:108) at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:76) at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:245) at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100) at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:82) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100) at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100) at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100) at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:197) at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:502) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ... 1 more

也不是很严重的问题（对于我）就是看着比较难受

在自己的电脑上测试没有问题，在腾讯云服务器出现了这个问题

Windows Server 2019 Java 17.0.1 mirai 2.9.0-M1

在消息链中获取到imageId，根据imageId构造Image对象，通过String imageUrl = Image.queryUrl(image);获取下载链接，下载链接打不开
7062f0e7-d7e0-440e-b44e-698c627d78ed-image.png

mirai-core 版本

2.16.0

bot-protocol

ANDROID_PAD

复现代码：

String imageId = "{57454715-A857-BAD2-D863-CA717CB64A5B}.jpg"; Image.Builder builder = Image.newBuilder(imageId); builder.setType(ImageType.valueOf(imageMessage.getImageType())); builder.setWidth(imageMessage.getWidth()); builder.setHeight(imageMessage.getHeight()); builder.setSize(imageMessage.getSize()); builder.setEmoji(imageMessage.getEmoji()); Image image = builder.build(); String imageUrl = Image.queryUrl(image);

String imageUrl = Image.queryUrl(image);

System.out.println(imageUrl);
输出的链接打开显示找不到页面。上周同样的代码获取到的链接打开可以看到我想要获取的图片。
具体链接如下
http://gchat.qpic.cn/gchatpic_new/2937718557/0-0-9857B3036B0AAFACC984B103F9A38186/0?term=2
具体代码如下
acbbf4af-891c-4b62-9cfb-f436b5ae8288-7a996b51a45c44d883565e45f9cde27e.png

有java开发使用mocking相关的demo吗？
现在连mockbot都创建不出来😭

QQ截图20240617005708.png
求助，把java版本降低到17后一直打不开mcl

2024-03-17 15:03:44 E/main: Failed to init MiraiConsole. net.mamoe.mirai.console.plugin.loader.PluginLoadException: Exception while loading QSign v1.3.0 at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.load(BuiltInJvmPluginLoaderImpl.kt:373) at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.load(BuiltInJvmPluginLoaderImpl.kt:40) at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.load(JvmPluginLoader.kt) at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.load(JvmPluginLoader.kt:54) at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.loadPluginNoEnable(PluginManagerImpl.kt:100) at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.loadAllPluginsUsingBuiltInLoaders$mirai_console(PluginManagerImpl.kt:164) at net.mamoe.mirai.console.internal.MiraiConsoleImplementationBridge.doStart$mirai_console(MiraiConsoleImplementationBridge.kt:303) at net.mamoe.mirai.console.MiraiConsoleImplementation$Companion.start(MiraiConsoleImplementation.kt:512) at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon(MiraiConsoleTerminalLoader.kt:182) at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon$default(MiraiConsoleTerminalLoader.kt:181) at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.main(MiraiConsoleTerminalLoader.kt:59) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.itxtech.mcl.Utility.bootJars(Utility.java:86) at org.itxtech.mcl.Utility.bootJars(Utility.java:76) at org.itxtech.mcl.Utility.bootMirai(Utility.java:98) at org.itxtech.mcl.module.builtin.Boot.boot(Boot.java:113) at org.itxtech.mcl.module.ModuleManager.phaseBoot(ModuleManager.java:123) at org.itxtech.mcl.Loader.lambda$start$4(Loader.java:196) at org.itxtech.mcl.Loader.tryCatching(Loader.java:151) at org.itxtech.mcl.Loader.start(Loader.java:196) at org.itxtech.mcl.Loader.main(Loader.java:84) Caused by: kotlin.UninitializedPropertyAccessException: lateinit property CONFIG has not been initialized at qsign-1.3.0.mirai2.jar//DataKt.getCONFIG(Data.kt:5) at qsign-1.3.0.mirai2.jar//top.mrxiaom.qsign.QSignService$Factory$Companion.loadConfigFromFile(QSignService.kt:242) at qsign-1.3.0.mirai2.jar//top.mrxiaom.qsign.QSignService$Factory$Companion.init(QSignService.kt:218) at qsign-1.3.0.mirai2.jar//top.mrxiaom.qsign.PluginMain.onLoad(PluginMain.kt:45) at net.mamoe.mirai.console.internal.plugin.JvmPluginInternal.internalOnLoad$mirai_console(JvmPluginInternal.kt:388) at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.load(BuiltInJvmPluginLoaderImpl.kt:371) ... 23 more

07:22:32 [DefaultDispatcher-worker-3] WARN com.github.unidbg.AbstractEmulator - emulate RX@0x4022e238[libfekit.so]0x22e238 exception sp=unidbg@0xbfffec20, msg=mem_write address=0x409d6000, offset=4ms 07:22:32 [DefaultDispatcher-worker-3] WARN com.github.unidbg.linux.ARM64SyscallHandler - handleInterrupt intno=2, NR=-128400, svcNumber=0x19e, PC=unidbg@0xfffe0a74, LR=RX@0x402330cc[libfekit.so]0x2330cc, syscall=null com.github.unidbg.arm.backend.BackendException: mem_write address=0x409d6000 at com.github.unidbg.arm.backend.Unicorn2Backend.mem_write(Unicorn2Backend.java:129) at com.github.unidbg.pointer.UnidbgPointer.write(UnidbgPointer.java:180) at com.github.unidbg.linux.android.dvm.DalvikVM64$159.handle(DalvikVM64.java:2553) at com.github.unidbg.linux.ARM64SyscallHandler.hook(ARM64SyscallHandler.java:121) at com.github.unidbg.arm.backend.Unicorn2Backend$11.hook(Unicorn2Backend.java:347) at com.github.unidbg.arm.backend.unicorn.Unicorn$NewHook.onInterrupt(Unicorn.java:109) at com.github.unidbg.arm.backend.unicorn.Unicorn.emu_start(Native Method) at com.github.unidbg.arm.backend.unicorn.Unicorn.emu_start(Unicorn.java:312) at com.github.unidbg.arm.backend.Unicorn2Backend.emu_start(Unicorn2Backend.java:384) at com.github.unidbg.AbstractEmulator.emulate(AbstractEmulator.java:380) at com.github.unidbg.thread.Function64.run(Function64.java:39) at com.github.unidbg.thread.MainTask.dispatch(MainTask.java:19) at com.github.unidbg.thread.UniThreadDispatcher.run(UniThreadDispatcher.java:175) at com.github.unidbg.thread.UniThreadDispatcher.runMainForResult(UniThreadDispatcher.java:99) at com.github.unidbg.AbstractEmulator.runMainForResult(AbstractEmulator.java:340) at com.github.unidbg.arm.AbstractARM64Emulator.eFunc(AbstractARM64Emulator.java:262) at com.github.unidbg.Module.emulateFunction(Module.java:163) at com.github.unidbg.linux.android.dvm.DvmObject.callJniMethod(DvmObject.java:135) at com.github.unidbg.linux.android.dvm.DvmObject.callJniMethodObject(DvmObject.java:93) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:54) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)

之前也报错过，信息好像有点不一样

21:08:00[scheduling-1] WARN org.mybatis.spring.mapper.ClassPathMapperScanner - No MyBatis mapper was found in '[mikulink.mapper]' package. Please check your configuration. 21:10:00[scheduling-1] WARN org.mybatis.spring.mapper.ClassPathMapperScanner - No MyBatis mapper was found in '[mikulink.mapper]' package. Please check your configuration. 21:30:05[DefaultDispatcher-worker-1] WARN com.github.unidbg.linux.ARM64SyscallHandler - handleInterrupt intno=2, NR=-128160, svcNumber=0x1ad, PC=unidbg@0xfffe0b64, LR=RX@0x40296b48[libfekit.so]0x296b48, syscall=null com.github.unidbg.arm.backend.BackendException: mem_write address=0x409d5000 at com.github.unidbg.arm.backend.Unicorn2Backend.mem_write(Unicorn2Backend.java:129) at com.github.unidbg.pointer.UnidbgPointer.write(UnidbgPointer.java:180) at com.github.unidbg.linux.android.dvm.array.ByteArray._GetArrayCritical(ByteArray.java:34) at com.github.unidbg.linux.android.dvm.DalvikVM64$174.handle(DalvikVM64.java:2761) at com.github.unidbg.linux.ARM64SyscallHandler.hook(ARM64SyscallHandler.java:121) at com.github.unidbg.arm.backend.Unicorn2Backend$11.hook(Unicorn2Backend.java:347) at com.github.unidbg.arm.backend.unicorn.Unicorn$NewHook.onInterrupt(Unicorn.java:109) at com.github.unidbg.arm.backend.unicorn.Unicorn.emu_start(Native Method) at com.github.unidbg.arm.backend.unicorn.Unicorn.emu_start(Unicorn.java:312) at com.github.unidbg.arm.backend.Unicorn2Backend.emu_start(Unicorn2Backend.java:384) at com.github.unidbg.AbstractEmulator.emulate(AbstractEmulator.java:380) at com.github.unidbg.thread.Function64.run(Function64.java:39) at com.github.unidbg.thread.MainTask.dispatch(MainTask.java:19) at com.github.unidbg.thread.UniThreadDispatcher.run(UniThreadDispatcher.java:175) at com.github.unidbg.thread.UniThreadDispatcher.runMainForResult(UniThreadDispatcher.java:99) at com.github.unidbg.AbstractEmulator.runMainForResult(AbstractEmulator.java:340) at com.github.unidbg.arm.AbstractARM64Emulator.eFunc(AbstractARM64Emulator.java:262) at com.github.unidbg.Module.emulateFunction(Module.java:163) at com.github.unidbg.linux.android.dvm.DvmObject.callJniMethod(DvmObject.java:135) at com.github.unidbg.linux.android.dvm.DvmObject.callJniMethodObject(DvmObject.java:93) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:54) at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56) at com.tencent.mobileqq.sign.QQSecuritySign.getSign$default(QQSecuritySign.kt:51) at moe.fuqiuluo.api.UnidbgFetchQSign.sign(UnidbgFetchQSign.kt:177) at moe.fuqiuluo.api.UnidbgFetchQSign$sign$1.invokeSuspend(UnidbgFetchQSign.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:284) at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:85) at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59) at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source) at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38) at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source) at top.mrxiaom.qsign.QSignService.qSecurityGetSign(QSignService.kt:129) at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.buildRawUniPacket(OutgoingPacket.kt:139) at net.mamoe.mirai.internal.network.protocol.packet.chat.receive.MessageSvcPbSendMsg.createToGroupImpl$mirai_core(MessageSvc.PbSendMsg.kt:744) at net.mamoe.mirai.internal.network.protocol.packet.chat.receive.MessageSvc_PbSendMsgKt.createToGroup(MessageSvc.PbSendMsg.kt:585) at net.mamoe.mirai.internal.message.protocol.outgoing.GroupMessageProtocolStrategy.createPacketsForGeneralMessage$suspendImpl(MessageProtocolStrategy.kt:150) at net.mamoe.mirai.internal.message.protocol.outgoing.GroupMessageProtocolStrategy.createPacketsForGeneralMessage(MessageProtocolStrategy.kt) at net.mamoe.mirai.internal.message.protocol.outgoing.GroupMessageProtocolStrategy.createPacketsForGeneralMessage(MessageProtocolStrategy.kt:139) at net.mamoe.mirai.internal.message.protocol.impl.GeneralMessageSenderProtocol$GeneralMessageSender.process(GeneralMessageSenderProtocol.kt:66) at net.mamoe.mirai.internal.message.protocol.outgoing.OutgoingMessageProcessorAdapter.process(OutgoingMessagePipelineProcessor.kt:26) at net.mamoe.mirai.internal.message.protocol.outgoing.OutgoingMessageProcessorAdapter.process(OutgoingMessagePipelineProcessor.kt:20) at net.mamoe.mirai.internal.pipeline.AbstractProcessorPipeline.process$suspendImpl(ProcessorPipeline.kt:287) at net.mamoe.mirai.internal.pipeline.AbstractProcessorPipeline.process(ProcessorPipeline.kt) at net.mamoe.mirai.internal.message.protocol.MessageProtocolFacadeImpl.preprocessAndSendOutgoingImpl(MessageProtocolFacade.kt:361) at net.mamoe.mirai.internal.message.protocol.MessageProtocolFacadeImpl.preprocessAndSendOutgoing(MessageProtocolFacade.kt:345) at net.mamoe.mirai.internal.message.protocol.MessageProtocolFacade$INSTANCE.preprocessAndSendOutgoing(MessageProtocolFacade.kt) at net.mamoe.mirai.internal.contact.AbstractUserKt.sendMessageImpl(AbstractUser.kt:263) at net.mamoe.mirai.internal.contact.CommonGroupImpl.sendMessage$suspendImpl(GroupImpl.kt:221) at net.mamoe.mirai.internal.contact.CommonGroupImpl.sendMessage(GroupImpl.kt) at net.mamoe.mirai.contact.Group$sendMessage$1.invoke(Group.kt) at net.mamoe.mirai.contact.Group$sendMessage$1.invoke(Group.kt) at kotlin.coroutines.intrinsics.IntrinsicsKt__IntrinsicsJvmKt$createCoroutineUnintercepted$$inlined$createCoroutineFromSuspendFunction$IntrinsicsKt__IntrinsicsJvmKt$1.invokeSuspend(IntrinsicsJvm.kt:205) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlin.coroutines.ContinuationKt.startCoroutine(Continuation.kt:115) at me.him188.kotlin.jvm.blocking.bridge.internal.RunSuspendKt.$runSuspend$(RunSuspend.kt:18) at net.mamoe.mirai.contact.Group.sendMessage(Group.kt) at mikulink.command.CommandConfig.group(CommandConfig.java:203) at mikulink.event.MessageEvents.onGroupMessage(MessageEvents.java:160) at jdk.internal.reflect.GeneratedMethodAccessor311.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at net.mamoe.mirai.internal.event.JvmMethodListenersInternalKt.registerEventHandler$callMethod$invokeWithErrorReport(JvmMethodListenersInternal.kt:140) at net.mamoe.mirai.internal.event.JvmMethodListenersInternalKt.access$registerEventHandler$callMethod$invokeWithErrorReport(JvmMethodListenersInternal.kt:1) at net.mamoe.mirai.internal.event.JvmMethodListenersInternalKt$registerEventHandler$callMethod$2.invokeSuspend(JvmMethodListenersInternal.kt:154) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42) at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) Caused by: unicorn.UnicornException: Invalid memory write (UC_ERR_WRITE_UNMAPPED) at com.github.unidbg.arm.backend.unicorn.Unicorn.mem_write(Native Method) at com.github.unidbg.arm.backend.unicorn.Unicorn.mem_write(Unicorn.java:223) at com.github.unidbg.arm.backend.Unicorn2Backend.mem_write(Unicorn2Backend.java:127) ... 73 common frames omitted

如图
屏幕截图 2024-03-16 170359.png 屏幕截图 2024-03-16 170506.png

回复: Mirai Administrator 机器人管理插件，好友/群管理，黑名单，宵禁
354d0780-a11b-4f5a-a974-4871dca2d1f5-image.png 设置了管理员后为什么还提示没有权限?

为啥我用 [post]/verify接口 返回的是空文本
状态码为415
而且返回头是

HTTP/1.1 415 Unsupported Media Type
Date: Wed, 07 Feb 2024 06:49:40 GMT
Server: Ktor/2.1.1
Content-Length: 0

提交的内容为
{
"verifyKey": "【我的key，此处略】"
}

我没改过文件名，它自己就是这样的，如图：
85bdcd3f-1e8f-4f60-91bf-f736852153da-image.png
内容：
cbba76db-98ad-4b6e-ac6a-fe430f5a2fba-image.png
不过这是个小小bug就是了