现在登录基本靠玄学
神迹！！！
32418a45-5632-4bf7-b48e-3717156efc85-image.png MPLBYK7DSY{`57HYLG6.png

大概实现逻辑是使用 腾讯云NLP聊天返回的值再用腾讯云的TTS转化成mp3 文件
然后转码成arm 再发送出去
Tim 的手机版可以听到语音 tim的电脑版不行 苹果的正常版本qq也不行
91bd22a1-2e15-46a8-8421-a932d2723fb7-图片.png

我按照操作示例，修改了config.json文件，但是升级不到2.15.0-RC升级到的是2.15.0-M1，fix-protocol-version V1.8.0版本，打开mcl就提示“ W/fix-protocol-version: 注册服务失败，请在 2.15.0-dev-98 或更高版本下运行”，所以我要怎么升级到RC版

如题，MCL下载插件的命令：

./mcl --update-package 包名 --channel maven

中【包名】应该如何查看？

如题

如何更新到自定义的版本

Login failed: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below.
2023-06-22 19:20:49 E/console: net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below.
net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below.
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:262)
at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:247)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
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)
Suppressed: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(114514), code=45, title=禁止登录, message=你的帐号涉嫌违规被限制在非常用设备登录，请更换常用设备后重新登 录并根据提示进行解封。, errorInfo=)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:489)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33)
at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
... 5 more
Suppressed: java.lang.IllegalStateException: Fast login failed: Error(bot=Bot(114514), code=40, title=安全提醒, message=请确认你输入了正确的帐号。该帐号存在被盗风险，已进入保护模 式，请前往安全中心恢复。, errorInfo=)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl.doLogin(SsoProcessor.kt:527)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33)
at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
... 5 more
Caused by: [CIRCULAR REFERENCE: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(114514), code=45, title=禁止登录, message=你的帐号涉嫌违规被限制在非常用设备登录，请更换常用 设备后重新登录并根据提示进行解封。, errorInfo=)]

手机打开后是：
因涉嫌异常使用行为（如涉嫌批量登录等业务违规操作，传播违法违规信息或组织相关活动）被暂时冻结QQ客户端登录。
也有和我在同一时期被一样封禁的人，打电话给客服，客服说使用了外挂程序，第三方插件和程序，并且已经检测出违规行为，是因为qq号风控程度高被风控，还是因为新协议的问题？

如题，更新到2.15.0-M1版本后无法进入登录验证，出现报错

2023-06-21 21:42:20 E/main: net.mamoe.mirai.internal.network.auth.ProducerFailureException

完整信息如下

=================================[ Mirai console 2.15.0-M1 ]================================== __ __ __ __ ______ __ | \ / \ \ | \/ \ | \ | ▓▓\ / ▓▓\▓▓ ______ ______ \▓▓ ▓▓▓▓▓▓\ ______ _______ _______ ______ | ▓▓ ______ | ▓▓▓\ / ▓▓▓ \/ \ | \| \ ▓▓ \▓▓/ \| \ / \/ \| ▓▓/ \ | ▓▓▓▓\ ▓▓▓▓ ▓▓ ▓▓▓▓▓▓\ \▓▓▓▓▓▓\ ▓▓ ▓▓ | ▓▓▓▓▓▓\ ▓▓▓▓▓▓▓\ ▓▓▓▓▓▓▓ ▓▓▓▓▓▓\ ▓▓ ▓▓▓▓▓▓\ | ▓▓\▓▓ ▓▓ ▓▓ ▓▓ ▓▓ \▓▓/ ▓▓ ▓▓ ▓▓ __| ▓▓ | ▓▓ ▓▓ | ▓▓\▓▓ \| ▓▓ | ▓▓ ▓▓ ▓▓ ▓▓ | ▓▓ \▓▓▓| ▓▓ ▓▓ ▓▓ | ▓▓▓▓▓▓▓ ▓▓ ▓▓__/ \ ▓▓__/ ▓▓ ▓▓ | ▓▓_\▓▓▓▓▓▓\ ▓▓__/ ▓▓ ▓▓ ▓▓▓▓▓▓▓▓ | ▓▓ \▓ | ▓▓ ▓▓ ▓▓ \▓▓ ▓▓ ▓▓\▓▓ ▓▓\▓▓ ▓▓ ▓▓ | ▓▓ ▓▓\▓▓ ▓▓ ▓▓\▓▓ \ \▓▓ \▓▓\▓▓\▓▓ \▓▓▓▓▓▓▓\▓▓ \▓▓▓▓▓▓ \▓▓▓▓▓▓ \▓▓ \▓▓\▓▓▓▓▓▓▓ \▓▓▓▓▓▓ \▓▓ \▓▓▓▓▓▓▓ 2023-06-21 21:42:16 I/main: Backend: version 2.15.0-M1, built on 2023-03-21 22:16:35. 2023-06-21 21:42:16 I/main: Frontend Terminal: version 2.15.0-M1, provided by Mamoe Technologies 2023-06-21 21:42:16 I/main: Welcome to visit https://mirai.mamoe.net/ 2023-06-21 21:42:18 I/plugin: Successfully loaded plugin mirai-device-generator v1.1.3 2023-06-21 21:42:18 I/fix-protocol-version: 协议版本检查更新... 2023-06-21 21:42:18 I/fix-protocol-version: ANDROID_PAD load from file:///home/loik/android_pad.json 2023-06-21 21:42:18 I/fix-protocol-version: 注册服务... 2023-06-21 21:42:18 W/fix-protocol-version: 注册服务失败，请在 2.15.0-dev-98 或更高版本下运行 2023-06-21 21:42:18 I/plugin: Successfully loaded plugin fix-protocol-version v1.8.0 2023-06-21 21:42:18 I/plugin: Successfully loaded plugin mirai-api-http v2.9.1 2023-06-21 21:42:19 I/plugin: Successfully loaded plugin mirai-login-solver-sakura v0.0.10 2023-06-21 21:42:19 I/plugin: Successfully loaded plugin MCL Addon v2.1.1 2023-06-21 21:42:19 I/main: Prepared built-in commands: autoLogin, help, login, logout, permission, status, stop 2023-06-21 21:42:19 I/fix-protocol-version: 当前各协议版本日期: ANDROID_PHONE 8.9.58.11170 2023-05-19T11:35+08:00 ANDROID_PAD 8.8.88.7083 2022-03-23T11:01:55+08:00 ANDROID_WATCH 2.0.8 2019-06-03T20:25:31+08:00 IPAD 8.9.33.614 2021-12-31T11:36:26+08:00 MACOS 6.7.9 1970-01-01T08:00+08:00 2023-06-21 21:42:19 I/Mirai HTTP API: ******************************************************** 2023-06-21 21:42:19 I/MahKtorAdapter[http]: Autoreload is disabled because the development mode is off. 2023-06-21 21:42:19 I/MahKtorAdapter[http]: Application started in 0.126 seconds. 2023-06-21 21:42:20 I/MahKtorAdapter[http]: Responding at http://0.0.0.0:8888 2023-06-21 21:42:20 I/http adapter: >>> [http adapter] is listening at http://0.0.0.0:8888 2023-06-21 21:42:20 I/MahKtorAdapter[ws]: Autoreload is disabled because the development mode is off. 2023-06-21 21:42:20 I/MahKtorAdapter[ws]: Application started in 0.023 seconds. 2023-06-21 21:42:20 I/MahKtorAdapter[ws]: Responding at http://localhost:8080 2023-06-21 21:42:20 I/ws adapter: >>> [ws adapter] is listening at ws://localhost:8080 2023-06-21 21:42:20 I/Mirai HTTP API: Http api server is running with verifyKey: 1234567890 2023-06-21 21:42:20 I/Mirai HTTP API: adaptors: [http,ws] 2023-06-21 21:42:20 I/Mirai HTTP API: ******************************************************** 2023-06-21 21:42:20 I/MCL Addon: iTXTech MCL Version: 2.1.2-61c8bd8 2023-06-21 21:42:20 W/MCL Addon: iTXTech Soyuz 未安装，Soyuz MCL Handler 特性已禁用 2023-06-21 21:42:20 I/main: 5 plugin(s) enabled. 2023-06-21 21:42:20 I/main: Auto-login 911986889, protocol: ANDROID_PAD, heartbeatStrategy: STAT_HB 2023-06-21 21:42:20 E/main: net.mamoe.mirai.internal.network.auth.ProducerFailureException net.mamoe.mirai.internal.network.auth.ProducerFailureException at net.mamoe.mirai.internal.network.auth.CoroutineOnDemandValueScope.receiveOrNull(CoroutineOnDemandValueScope.kt:152) at net.mamoe.mirai.internal.network.auth.AuthControl.acquireAuth(AuthControl.kt:98) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:219) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$login$1.invokeSuspend(SsoProcessor.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:138) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:112) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.access$loop(SuspendFunctionGun.kt:14) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:62) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:138) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:112) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.access$loop(SuspendFunctionGun.kt:14) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:62) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:138) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:112) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.access$loop(SuspendFunctionGun.kt:14) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:62) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:138) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:112) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.access$loop(SuspendFunctionGun.kt:14) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:62) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:138) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:112) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.access$loop(SuspendFunctionGun.kt:14) at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:62) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) 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: net.mamoe.mirai.internal.network.auth.IllegalProducerStateException: ProducerReady at net.mamoe.mirai.internal.network.auth.CoroutineOnDemandValueScope$Producer.emit(CoroutineOnDemandValueScope.kt:76) at net.mamoe.mirai.internal.network.auth.AuthControl$userDecisions$1$sessionImpl$1.authByPassword-vaT0TR8(AuthControl.kt:46) at net.mamoe.mirai.internal.network.auth.DefaultBotAuthorizationFactoryImpl$byPassword$1.authorize(DefaultBotAuthorizationFactoryImpl.kt:37) at net.mamoe.mirai.internal.network.auth.BotAuthorizationWithSecretsProtection.authorize(BotAuthSession.kt:47) at net.mamoe.mirai.internal.network.auth.AuthControl$userDecisions$1.invokeSuspend(AuthControl.kt:77) at net.mamoe.mirai.internal.network.auth.AuthControl$userDecisions$1.invoke(AuthControl.kt) at net.mamoe.mirai.internal.network.auth.AuthControl$userDecisions$1.invoke(AuthControl.kt) at net.mamoe.mirai.internal.network.auth.CoroutineOnDemandValueScope$Producer$1.invokeSuspend(CoroutineOnDemandValueScope.kt:50) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ... 5 more 2023-06-21 21:42:20 V/Bot.911986889: Event: net.mamoe.mirai.console.events.AutoLoginEvent$Failure@56881196 2023-06-21 21:42:20 I/main: mirai-console started successfully. 2023-06-21 21:42:20 I/Bot.911986889: Bot cancelled: Bot closed

版本：mirai 2.15.0-M1
protocol:ANDROID_PAD
安装的插件：
fix-protocol-version-1.8.0.mirai2.jar
mcl-addon-2.1.1.jar
mirai-api-http-2.9.1.mirai2.jar
mirai-device-generator-1.1.3.mirai2.jar
mirai-login-solver-sakura-0.0.10.mirai2.jar
系统： Ubuntu20.04
抱歉由于知识缺乏，无法提供更多信息，安装过程中都选择的默认选项。
论坛中有关于这个问题的帖子，我也阅读了那篇帖子以及相关的github issue，但因为我对github不甚熟悉，仅凭原先的教程没弄明白如何安装2.15.0-dev-98，恰巧今晚发布了v2.15.0-RC，提到已经包含了2.15.0-dev-98的更新内容，我尝试更新到这个版本，但是似乎是更新失败了？我已经将config.json里的maven-stable全部替换成了maven，并执行了./mcl -u，为何版本显示的还是2.15.0-M1呢？上面的完整信息就是更新之后截取的log文件，希望哪位大佬解惑，感谢！

我忘了如果安卓手机客户端登录了qq，mirai使用ANDROID_PAD还能不能同时在线。
刚才使用了最新版在mirai登录了ANDROID_PAD，手机客户端就下线了，pc上面的还没下线。
是我记错了还是qq更新策略了？🤯

纯新手一名，只会组装插件。想要一个玩1A2B 猜数字的插件，然后到GIT上面下载了一个插件，但是说明和源代码里都没有找到游戏口令的信息。麻烦大佬帮忙看看是不是项目写得有问题啊。
插件的GIT信息如下：
https://github.com/kono-dada/mirai_guess_number

如果有大佬写过类似的1A2B猜数字插件还麻烦帮忙给个JAR

2023-06-18 21:34:48 I/main: Starting mirai-console...
2023-06-18 21:34:48 I/main:

===============================[ Mirai console 2.15.0-dev-98 ]================================

| \ / \ \ | / \ |
| ▓▓\ / ▓▓\▓▓ ______ ______ \▓▓ ▓▓▓▓▓▓\ ______ _______ _______ ______ | ▓▓ ______
| ▓▓▓\ / ▓▓▓ / \ | | \ ▓▓ \▓▓/ | \ / / | ▓▓/
| ▓▓▓▓\ ▓▓▓▓ ▓▓ ▓▓▓▓▓▓\ \▓▓▓▓▓▓\ ▓▓ ▓▓ | ▓▓▓▓▓▓\ ▓▓▓▓▓▓▓\ ▓▓▓▓▓▓▓ ▓▓▓▓▓▓\ ▓▓ ▓▓▓▓▓▓
| ▓▓\▓▓ ▓▓ ▓▓ ▓▓ ▓▓ \▓▓/ ▓▓ ▓▓ ▓▓ | ▓▓ | ▓▓ ▓▓ | ▓▓\▓▓ | ▓▓ | ▓▓ ▓ ▓ ▓▓ ▓▓
| ▓▓ \▓▓▓| ▓▓ ▓▓ ▓▓ | ▓▓▓▓▓▓▓ ▓▓ ▓▓/ \ ▓▓__/ ▓▓ ▓▓ | ▓▓_\▓▓▓▓▓▓\ ▓▓__/ ▓▓ ▓▓ ▓▓▓▓▓▓▓▓
| ▓▓ \▓ | ▓▓ ▓▓ ▓▓ \▓▓ ▓▓ ▓▓\▓▓ ▓▓\▓▓ ▓▓ ▓▓ | ▓▓ ▓▓\▓▓ ▓▓ ▓▓\▓▓
\▓▓ \▓▓\▓▓\▓▓ \▓▓▓▓▓▓▓\▓▓ \▓▓▓▓▓▓ \▓▓▓▓▓▓ \▓▓ \▓▓\▓▓▓▓▓▓▓ \▓▓ ▓▓▓▓ \▓▓ \▓▓▓▓▓▓▓

2023-06-18 21:34:48 I/main: Backend: version 2.15.0-dev-98, built on 2023-06-04 07:47:48.
2023-06-18 21:34:48 I/main: Frontend Terminal: version 2.15.0-dev-98, provided by Mamoe Technologies
2023-06-18 21:34:48 I/main: Welcome to visit https://mirai.mamoe.net/
2023-06-18 21:34:50 I/fix-protocol-version: 协议版本检查更新...
2023-06-18 21:35:29 I/fix-protocol-version: 注册服务...
2023-06-18 21:35:29 I/plugin: Successfully loaded plugin fix-protocol-version v1.7.1
2023-06-18 21:35:29 W/MiraiNative: 当前运行环境 64 可能不与 Mirai Native 兼容，推荐使用 32位 JRE 运行 Mirai Native。
2023-06-18 21:35:29 W/MiraiNative: 如果您正在开发或调试其他环境下的 Mirai Native，请忽略此警告。
2023-06-18 21:35:29 I/plugin: Successfully loaded plugin MiraiNative v2.0.0-cssxsh
2023-06-18 21:35:29 I/plugin: Successfully loaded plugin MCL Addon v2.1.1
2023-06-18 21:35:30 I/main: Prepared built-in commands: autoLogin, help, login, logout, permission, status, stop
2023-06-18 21:35:30 I/fix-protocol-version: 当前各协议版本日期:
ANDROID_PHONE 8.9.58.11170 2023-05-19T11:35+08:00
ANDROID_PAD 8.8.88.7083 2022-03-23T11:01:55+08:00
ANDROID_WATCH 2.0.8 2019-06-03T20:25:31+08:00
IPAD 8.9.33.614 2021-12-31T11:36:26+08:00
MACOS 6.7.9 1970-01-01T08:00+08:00

2023-06-18 21:35:30 I/MiraiNative: 正在加载 Mirai Native Bridge C:\Users\Administrator\Desktop\00\data\org.itxtech.mirainative\CQP.dll
2023-06-18 21:35:30 E/MiraiNative: java.lang.UnsatisfiedLinkError: C:\Users\Administrator\Desktop\00\data\org.itxtech.mirainative\CQP.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
java.lang.UnsatisfiedLinkError: C:\Users\Administrator\Desktop\00\data\org.itxtech.mirainative\CQP.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
at java.base/jdk.internal.loader.NativeLibraries.load(Native Method)
at java.base/jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open(NativeLibraries.java:388)
at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:232)
at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:174)
at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2389)
at java.base/java.lang.Runtime.load0(Runtime.java:755)
at java.base/java.lang.System.load(System.java:1953)
at mirai-native-2.0.0.mirai2.jar//org.itxtech.mirainative.manager.LibraryManager.load(LibraryManager.kt:33)
at mirai-native-2.0.0.mirai2.jar//org.itxtech.mirainative.MiraiNative.checkNativeLibs(MiraiNative.kt:86)
at mirai-native-2.0.0.mirai2.jar//org.itxtech.mirainative.MiraiNative.onEnable(MiraiNative.kt:170)
at net.mamoe.mirai.console.internal.plugin.JvmPluginInternal.internalOnEnable$mirai_console(JvmPluginInternal.kt:237)
at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.enable(BuiltInJvmPluginLoaderImpl.kt:308)
at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.enable(BuiltInJvmPluginLoaderImpl.kt:39)
at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.enable(JvmPluginLoader.kt)
at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.enable(JvmPluginLoader.kt:54)
at net.mamoe.mirai.console.plugin.PluginManager.enablePlugin(PluginManager.kt:173)
at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.enableAllLoadedPlugins$mirai_console(PluginManagerImpl.kt:181)
at net.mamoe.mirai.console.internal.MiraiConsoleImplementationBridge.doStart$mirai_console(MiraiConsoleImplementationBridge.kt:359)
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)

2023-06-18 21:35:30 E/MCL Addon: Mirai Console 并未通过 iTXTech Mirai Console Loader 加载。
2023-06-18 21:35:30 E/MCL Addon: 请访问 https://github.com/iTXTech/mirai-console-loader
2023-06-18 21:35:30 I/main: 2 plugin(s) enabled.
2023-06-18 21:35:30 I/main: mirai-console started successfully.

代码如上所示，求大佬帮助，用的JAVA17！

1.Mirai版本

===============================[ Mirai console 2.15.0-dev-98 ]================================ __ __ __ __ ______ __ | \ / \ \ | \/ \ | \ | ▓▓\ / ▓▓\▓▓ ______ ______ \▓▓ ▓▓▓▓▓▓\ ______ _______ _______ ______ | ▓▓ ______ | ▓▓▓\ / ▓▓▓ \/ \ | \| \ ▓▓ \▓▓/ \| \ / \/ \| ▓▓/ \ | ▓▓▓▓\ ▓▓▓▓ ▓▓ ▓▓▓▓▓▓\ \▓▓▓▓▓▓\ ▓▓ ▓▓ | ▓▓▓▓▓▓\ ▓▓▓▓▓▓▓\ ▓▓▓▓▓▓▓ ▓▓▓▓▓▓\ ▓▓ ▓▓▓▓▓▓\ | ▓▓\▓▓ ▓▓ ▓▓ ▓▓ ▓▓ \▓▓/ ▓▓ ▓▓ ▓▓ __| ▓▓ | ▓▓ ▓▓ | ▓▓\▓▓ \| ▓▓ | ▓▓ ▓ ▓ ▓▓ ▓▓ | ▓▓ \▓▓▓| ▓▓ ▓▓ ▓▓ | ▓▓▓▓▓▓▓ ▓▓ ▓▓__/ \ ▓▓__/ ▓▓ ▓▓ | ▓▓_\▓▓▓▓▓▓\ ▓▓__/ ▓▓ ▓▓ ▓▓▓▓▓▓▓▓ | ▓▓ \▓ | ▓▓ ▓▓ ▓▓ \▓▓ ▓▓ ▓▓\▓▓ ▓▓\▓▓ ▓▓ ▓▓ | ▓▓ ▓▓\▓▓ ▓▓ ▓▓\▓▓ \ \▓▓ \▓▓\▓▓\▓▓ \▓▓▓▓▓▓▓\▓▓ \▓▓▓▓▓▓ \▓▓▓▓▓▓ \▓▓ \▓▓\▓▓▓▓▓▓▓ \▓▓ ▓▓▓▓ \▓▓ \▓▓▓▓▓▓▓ 2023-06-15 13:09:43 I/main: Backend: version 2.15.0-dev-98, built on 2023-06-04 07:47:48. 2023-06-15 13:09:43 I/main: Frontend Terminal: version 2.15.0-dev-98, provided by Mamoe Technologies

2.协议版本信息

2023-06-15 13:10:31 I/fix-protocol-version: 当前各协议版本日期: ANDROID_PHONE 8.9.58.11170 2023-05-19T11:35+08:00 ANDROID_PAD 8.8.88.7083 2022-03-23T11:01:55+08:00 ANDROID_WATCH 2.0.8 2019-06-03T20:25:31+08:00 IPAD 8.9.33.614 2021-12-31T11:36:26+08:00 MACOS 6.7.9 1970-01-01T08:00+08:00

3.登录协议
密码登录(ANDROID_PAD)

4.出现问题
正常登录，正常收到消息，无法发送任何消息(类型皆为群消息)
(隐私内容已做处理,不影响错误判断)

2023-06-15 13:22:46 I/TLV544Provider: t544 command: 810_a 2023-06-15 13:22:46 I/Bot.1000000000: Saved account secrets to local cache for fast login. 2023-06-15 13:22:46 I/Bot.1000000000: Login successful. 2023-06-15 13:22:46 V/Bot.1000000000: Event: BotOnlineEvent(bot=Bot(1000000000)) 2023-06-15 13:22:46 V/Bot.1000000000: Event: BotReloginEvent(bot=Bot(1000000000), cause=null) 2023-06-15 13:22:46 I/Bot.1000000000: Reconnected successfully in 0.5s. 2023-06-15 13:23:15 V/Bot.1000000000: [GroupName(GroupID)] qing_zhou(uid) -> 不是 2023-06-15 13:23:21 V/Bot.1000000000: [BOT(GroupID)] anchor(uid) -> /mcadd sss:2077 2023-06-15 13:23:26 V/Bot.1000000000: [BOT(GroupID)] anchor(uid) -> /mcp 2023-06-15 13:23:27 V/Bot.1000000000: [GroupName(GroupID)] qing_zhou(uid) -> 1 2023-06-15 13:23:29 V/Bot.1000000000: [GroupName(GroupID)] qing_zhou(uid) -> [mirai:image:{91CF2379-72F6-24A9-F2C5-1E22FDD0CD3F}.jpg, width=440, height=429, size=10982, type=GIF, isEmoji=false] 2023-06-15 13:23:36 V/Bot.1000000000: [GroupName(GroupID)] CloudGFX(uid) -> /mcp 2023-06-15 13:23:39 V/Bot.1000000000: Group(GroupID) <- [mirai:at:uid] [mirai:image:{7536E3AB-151F-C9FB-DC2F-A381EFC870B7}.png, width=1000, height=400, size=64370, type=PNG, isEmoji=false]

倒数第一第二条消息即为群功能插件， "/mcp"指令触发机器人发送一张图片，后台日志正常，接收消息也正常，而无法正常发送消息。

设置guid值之后登陆不会出现滑块，也不容易登陆失败

如题
手上版本最高的也只到 Android 8.1 (MIUI 11)
but,Mirai-login-solver-sakura需要Android 9，所以有什么办法可以不用APP完成验证

07:37:00 [ERROR] Failed to fetch announcement for "org.bouncycastle:bcprov-jdk15on"
07:37:00 [ERROR] Failed to fetch MCL announcement.
07:37:00 [INFO] Verifying "net.mamoe:mirai-console" v2.14.0

07:37:03 [INFO] Verifying "org.bouncycastle:bcprov-jdk15on"
07:37:03 [ERROR] Failed to verify package "org.bouncycastle:bcprov-jdk15on"
07:37:03 [ERROR] javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
at java.net.http/jdk.internal.net.http.HttpClientImpl.send(HttpClientImpl.java:578)
at java.net.http/jdk.internal.net.http.HttpClientFacade.send(HttpClientFacade.java:123)
at org.itxtech.mcl.component.Repository.httpGet(Repository.java:211)
at org.itxtech.mcl.component.Repository.httpGet(Repository.java:206)
at org.itxtech.mcl.component.Repository.fetchPackage(Repository.java:84)
at org.itxtech.mcl.module.builtin.RepoCache$RepoWithCache.fetchPackage(RepoCache.java:88)
at org.itxtech.mcl.module.builtin.Updater.check(Updater.java:101)
at org.itxtech.mcl.module.builtin.Updater.load(Updater.java:60)
at org.itxtech.mcl.module.ModuleManager.phaseLoad(ModuleManager.java:117)
at org.itxtech.mcl.Loader.lambda$start$3(Loader.java:190)
at org.itxtech.mcl.Loader.tryCatching(Loader.java:151)
at org.itxtech.mcl.Loader.start(Loader.java:190)

我已经根据论坛公告上最新发布的关于解决"code=45"的办法去进行调整了。
但是很遗憾，还是"code=45"(233

现在，我想了解一下，在用基于Mirai框架的机器人的同学们，你们还有能正常使用的吗？

我这里指的能正常使用是指机器人可以正常登录上。

如题。。

由于我用其他协议、方法都是code=45，只能使用cssxsh大佬的临时解决方案(2.15.0-dev-98整合包)使用ANDROID_PAD协议。
最开始使用cssxsh的该整合包一切正常，没过多久(大概1天)就这样了，尝试过重启mirai-console，更换协议(无果)。
账号应该是被风控了吧？然后我尝试在Go-cqhttp里登录(ANDROID_WATCH协议)，可登录(方法是本地扫码，打包session等文件上传至服务器)，巧了，发送消息的时候，该账号可能被风控，发送消息失败。

昨天在拜读完“cssxsh”发布的那个公告后，我就在电脑和服务器上实操了一下，虽然在电脑上确实登录上去了，但是服务器上却出现了一些问题。



通过观察可以明显发现有些核心的依赖并没有完成下载，不知道是不是服务器网络的问题还是说需要去用别的方式进行设置呢？