Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: 请求 Discord 的 Webhook 时显示空指针错误但实际成功 #234

Closed
mxalbert1996 opened this issue Nov 11, 2022 · 8 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@mxalbert1996
Copy link

是否有人曾提过类似的问题

否(No)

升级到最新的版本是否存在这个问题

是(Yes)

是否已经查阅Wiki文档还未能解决的

是(Yes)

APP版本

v3.1.1

问题描述

设置好 Discord 的 Webhook 后按测试按钮时应用内报错“请求失败:空指针错误“,但实际消息成功发出。

复现步骤

  • 在 Discord 里创建一个 Webhook
  • 新建一个 Webhook 发送通道,Server 填入 Webhook 的 URL,Params 填 {"content":"[msg]"}
  • 按测试按钮

是否必现

是(Yes)

出现问题的手机信息

Google Pixel 6 Pro

出现问题的安卓版本、系统版本

Android 13

提供截图或视频

提供报错堆栈

No response

提供解决方案

No response

@mxalbert1996 mxalbert1996 added the bug Something isn't working label Nov 11, 2022
@pppscn
Copy link
Owner

pppscn commented Jan 28, 2023

提供一下完整的Webhook地址给我测试一下

@mxalbert1996
Copy link
Author

https://discord.com/api/webhooks/1068829528060858368/zHC7r3Vpnv3y3f1-4oypdZc9iRCGTx_VzHzVUVG3fT2l61BM69AlN9BWryzBETKVCQJU

@pppscn
Copy link
Owner

pppscn commented Jan 28, 2023

这个webhook一直返回的http code204,没有应答任何内容?

2023-01-28 22:26:55.359  9258-7113  WebhookFragment         com.idormy.sms.forwarder             D  WebhookSetting(method=POST, webServer=https://discord.com/api/webhooks/1068829528060858368/zHC7r3Vpnv3y3f1-4oypdZc9iRCGTx_VzHzVUVG3fT2l61BM69AlN9BWryzBETKVCQJU, secret=, webParams={"content":"[msg]"}, headers={})
2023-01-28 22:26:55.363  9258-7113  WebhookUtils            com.idormy.sms.forwarder             I  requestUrl:https://discord.com/api/webhooks/1068829528060858368/zHC7r3Vpnv3y3f1-4oypdZc9iRCGTx_VzHzVUVG3fT2l61BM69AlN9BWryzBETKVCQJU
2023-01-28 22:26:55.364  9258-7113  WebhookUtils            com.idormy.sms.forwarder             I  matches = []
2023-01-28 22:26:55.364  9258-7113  WebhookUtils            com.idormy.sms.forwarder             D  method = POST, Url = https://discord.com/api/webhooks/1068829528060858368/zHC7r3Vpnv3y3f1-4oypdZc9iRCGTx_VzHzVUVG3fT2l61BM69AlN9BWryzBETKVCQJU, bodyMsg = {"content":"19999999999\n【测试通道】恭喜您,该发送通道测试成功,请继续添加转发规则!\nSIM1_测试运营商_18888888888\n2023-01-28 22:26:55\npppscn的Mi 10S"}
2023-01-28 22:26:55.371  9258-7113  [XHttp]                 com.idormy.sms.forwarder             I  cacheMode=NO_CACHE
2023-01-28 22:26:55.372  9258-7113  [XHttp]                 com.idormy.sms.forwarder             D  --> Subscriber is onStart
2023-01-28 22:26:55.372  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  -------------------------------request-------------------------------
2023-01-28 22:26:55.373  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  --> POST https://discord.com/api/webhooks/1068829528060858368/zHC7r3Vpnv3y3f1-4oypdZc9iRCGTx_VzHzVUVG3fT2l61BM69AlN9BWryzBETKVCQJU http/1.1
2023-01-28 22:26:55.373  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	Accept: application/json
2023-01-28 22:26:55.373  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	body:{"content":"19999999999\n【测试通道】恭喜您,该发送通道测试成功,请继续添加转发规则!\nSIM1_测试运营商_18888888888\n2023-01-28 22:26:55\npppscn的Mi 10S"}
2023-01-28 22:26:55.373  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  --> END POST
2023-01-28 22:26:57.054  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  -------------------------------response-------------------------------
2023-01-28 22:26:57.054  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  <-- 204  https://discord.com/api/webhooks/1068829528060858368/zHC7r3Vpnv3y3f1-4oypdZc9iRCGTx_VzHzVUVG3fT2l61BM69AlN9BWryzBETKVCQJU (1680ms)
2023-01-28 22:26:57.054  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I   
2023-01-28 22:26:57.054  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	date: Sat, 28 Jan 2023 14:26:56 GMT
2023-01-28 22:26:57.054  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	content-type: text/html; charset=utf-8
2023-01-28 22:26:57.054  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	set-cookie: __dcfduid=d190ff209f1711edb8048684289118ec; Expires=Thu, 27-Jan-2028 14:26:56 GMT; Max-Age=157680000; Secure; HttpOnly; Path=/
2023-01-28 22:26:57.055  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	strict-transport-security: max-age=31536000; includeSubDomains; preload
2023-01-28 22:26:57.055  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	x-ratelimit-bucket: 3d2712a9e4fe17cc9d3fed4a8e672e5f
2023-01-28 22:26:57.055  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	x-ratelimit-limit: 5
2023-01-28 22:26:57.055  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	x-ratelimit-remaining: 4
2023-01-28 22:26:57.055  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	x-ratelimit-reset: 1674916018
2023-01-28 22:26:57.055  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	x-ratelimit-reset-after: 1
2023-01-28 22:26:57.055  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	via: 1.1 google
2023-01-28 22:26:57.055  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
2023-01-28 22:26:57.055  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	cf-cache-status: DYNAMIC
2023-01-28 22:26:57.055  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=JhTtk5aRpdyLeIoHpK%2FVj6Bdi8xdFsESnlbZtCpYD7CyLZago9d%2F9RdVID1N982vpWx7yX71kSBcPxawmzIdQ02nky%2BCArneqqYXlJlTrINqvg2O3bnvRr%2Bbs60q"}],"group":"cf-nel","max_age":604800}
2023-01-28 22:26:57.056  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
2023-01-28 22:26:57.056  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	x-content-type-options: nosniff
2023-01-28 22:26:57.056  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	set-cookie: __sdcfduid=d190ff209f1711edb8048684289118ec9163595a4c5e274db4d7c0ad793d9c4a6e8b81c80823fe03d4e8e0688f459abf; Expires=Thu, 27-Jan-2028 14:26:56 GMT; Max-Age=157680000; Secure; HttpOnly; Path=/
2023-01-28 22:26:57.056  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	set-cookie: __cfruid=f824b439c0c39c7cd67a22cda31e69e3d6f9f4e1-1674916016; path=/; domain=.discord.com; HttpOnly; Secure; SameSite=None
2023-01-28 22:26:57.056  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	server: cloudflare
2023-01-28 22:26:57.056  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	cf-ray: 790a67ef5c90a9a9-TPE
2023-01-28 22:26:57.056  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  	Cache-Control: no-cache
2023-01-28 22:26:57.056  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I   
2023-01-28 22:26:57.056  9258-3691  [XHttp]                 com.idormy.sms.forwarder             I  <-- END HTTP
2023-01-28 22:26:57.058  9258-9258  [XHttp]                 com.idormy.sms.forwarder             E  --> Subscriber is onError
2023-01-28 22:26:57.058  9258-9258  [XHttp]                 com.idormy.sms.forwarder             E  --> e instanceof ApiException, message:空指针错误
2023-01-28 22:26:57.058  9258-9258  WebhookUtils            com.idormy.sms.forwarder             E  Code:5010, Message:空指针错误

@mxalbert1996
Copy link
Author

对,HTTP 204 表示请求成功,似乎也没什么问题?

@pppscn
Copy link
Owner

pppscn commented Jan 28, 2023

看了一下只能先挂起了

http请求采用XHttp2框架(基于okhttp),只有 http 200 才认定为是 onSuccess , 高度封装的框架要改变这个逻辑,看起来不太容易,后续有想到好的方法时再说了

@pppscn
Copy link
Owner

pppscn commented Feb 5, 2023

暂时不处理

@pppscn pppscn closed this as completed Feb 5, 2023
@vicdorke
Copy link

vicdorke commented Apr 2, 2024

修bug呀

@pppscn pppscn reopened this Apr 8, 2024
pppscn added a commit that referenced this issue Apr 9, 2024
优化:服务端应答`Http 204 No Content`时特殊处理(更新日志状态为成功) #234
@pppscn
Copy link
Owner

pppscn commented Apr 9, 2024

暂时特殊处理,当服务端应答Http 204 No Content时 ,更新日志状态为成功

覆盖安装 每周构建版 试试

升级操作提示:

pppscn added a commit that referenced this issue Apr 9, 2024
优化:服务端应答`Http 204 No Content`时特殊处理(更新日志状态为成功) #234
@pppscn pppscn closed this as completed Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants