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

[Other]: The session whose notification type is queried using GetOneConversation cannot be queried #418

Closed
zhaolibo1989 opened this issue Nov 22, 2023 · 5 comments
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@zhaolibo1989
Copy link
Contributor

zhaolibo1989 commented Nov 22, 2023

What would you like to share?

使用 GetOneConversation 查通知类型的会话查不到。

代码版本 v3.4.0

SDK 在数据库中创建的会话 ID 示例:sn_openIMAdmin_10065

修改建议:

1

2

Additional information

No response

@zhaolibo1989 zhaolibo1989 added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 22, 2023
@cubxxw cubxxw changed the title [Other]: 使用 GetOneConversation 查通知类型的会话查不到 [Other]: The session whose notification type is queried using GetOneConversation cannot be queried Nov 22, 2023
@zhaolibo1989
Copy link
Contributor Author

@FGadvancer
sn_openIMAdmin_10065 这样的会话是使用服务器 API msg/send_msg 发送通知类型的消息(contentType=1400, sessionType=4)给用户产生的。
用户收到这样的会话消息后,打开并查看,APP 像使用普通会话一样使用 GetOneConversation 接口查询会话信息。我们就是这样发现这个情况的。

@kubbot
Copy link
Contributor

kubbot commented Nov 24, 2023

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


@FGadvancer
sn_openIMAdmin_10065 Such a session is generated by using the server API msg/send_msg to send a notification type message (contentType=1400, sessionType=4) to the user.
After the user receives such a session message, open and view it, and the APP uses the GetOneConversation interface to query the session information just like a normal session. This is how we found out about this situation.

@kubbot
Copy link
Contributor

kubbot commented Jan 23, 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 Jan 23, 2024
@kubbot
Copy link
Contributor

kubbot commented Jan 31, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as completed Jan 31, 2024
@github-actions github-actions bot reopened this Aug 8, 2024
@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 8, 2024
@skiffer-git
Copy link
Member

The latest version doesn't have this issue. Please go ahead and use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants