[BUG] After upgrading to 3.8, previous sessions cannot receive messages.

[bilicast]

OpenIM Server Version

3.8.0

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Docker Deployment

Bug Description and Steps to Reproduce

服务端从3.7升级到3.8后, 客户端未升级。以前的会话收不到消息, 新会话能正常工作。

服务端日志:

Screenshots Link

No response

[kubbot]

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.

[cipchk]

我的情况是哪怕客户端升级也是旧会话也是无法收到消息。

[kubbot]

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

---

In my case, even if the client is upgraded and the session is old, the message cannot be received.

[bilicast]

我的情况是哪怕客户端升级也是旧会话也是无法收到消息。

@cipchk 同样的问题，你的问题我们也遇到了。

[kubbot]

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

---

In my case, even if the client is upgraded and the session is old, the message cannot be received.

@cipchk We have the same problem as yours.

[cipchk]

@bilicast 现在如果调用 deleteConversationAndDeleteAllMsg 会导致 hasReadSeq must not be bigger than maxSeq，但是这种情况下很容易产生，比如当我清空 components 以后，而客户端有本地缓存，这就导致用户务必要清除本地数据才会正常。

[FGadvancer]

When you upgraded, did you encounter the issue shown in the image regarding the seq conversion? Ultimately, was the maximum seq for the conversation successfully converted into the seq collection? or you can take a screenshot regarding the data_version collection.

[skiffer-git]

It seems like you've deleted the data in Redis.