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

When the backend sends a message through RestAPI, there is no ex field, and after adding more ex fields to send the message, the front end cannot receive the ex field. #2135

Closed
BobBaoDengKe opened this issue Mar 20, 2024 · 4 comments
Labels
bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@BobBaoDengKe
Copy link

What happened?

后端通过RestAPI发送消息时,文档没有ex字段,发送者自己额外发送ex字段后,前端通过websocket也未拿到ex字段。

前端通过jssdk发送消息时是有ex字段的,使用docker部署,openim-server release-v3.4

image

What did you expect to happen?

希望发布新版本,加上ex字段

How can we reproduce it (as minimally and precisely as possible)?

Anything else we need to know?

No response

version

```console $ {name} version # paste output here 这个镜像版本:openim-server release-v3.4

Cloud provider

OS version

```console # On Linux: $ cat /etc/os-release # paste output here $ uname -a # paste output here # On Windows: C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture # paste output here ```

Install tools

@BobBaoDengKe BobBaoDengKe added the bug Categorizes issue or PR as related to a bug. label Mar 20, 2024
@kubbot kubbot changed the title 后端通过RestAPI发送消息时,没有ex字段,且自己多添加ex字段发送消息后,前端也收不到ex字段 When the backend sends a message through RestAPI, there is no ex field, and after adding more ex fields to send the message, the front end cannot receive the ex field. Mar 20, 2024
@kubbot
Copy link
Contributor

kubbot commented Mar 20, 2024

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

@kubbot
Copy link
Contributor

kubbot commented May 27, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot kubbot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 27, 2024
@skiffer-git
Copy link
Member

I recommend updating to release-v3.8. If you run into any new issues, please reopen this issue or create a new one.

@skiffer-git
Copy link
Member

{
"sendID": "openIMAdmin",
"recvID": "2839678182",
"groupID": "",
"senderNickname": "openIMAdmin-Gordon",
"senderFaceURL": "http://www.head.com",
"senderPlatformID": 1,
"content": {
"content": "hello!!"
},
"contentType": 101,
"sessionType": 1,
"isOnlineOnly": false,
"notOfflinePush": false,
"sendTime": 1695212630740,
"offlinePushInfo": {
"title": "send message",
"desc": "",
"ex": "",
"iOSPushSound": "default",
"iOSBadgeCount": true
},
"ex": "ex"
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants