You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the OpenIM server has been running for a while, due to certain reasons, the data on the server was lost. However, the conversation list and messages are still retained locally on the app side. If the app side calls the deleteConversationAndDeleteAllMsg interface to delete conversation records, it will prompt an error and cannot be deleted. Is there any other method to clear the local conversations and messages on the app side, apart from uninstalling and reinstalling the APP? I have checked your official documentation (https://docs.openim.io/zh-Hans/sdks/api/conversation/hideAllConversation) and found the prototype of the deleteAllConversationFromLocal interface, but I couldn't actually locate this interface.
What would you like to share?
After the OpenIM server has been running for a while, due to certain reasons, the data on the server was lost. However, the conversation list and messages are still retained locally on the app side. If the app side calls the deleteConversationAndDeleteAllMsg interface to delete conversation records, it will prompt an error and cannot be deleted. Is there any other method to clear the local conversations and messages on the app side, apart from uninstalling and reinstalling the APP? I have checked your official documentation (https://docs.openim.io/zh-Hans/sdks/api/conversation/hideAllConversation) and found the prototype of the deleteAllConversationFromLocal interface, but I couldn't actually locate this interface.
openim服务器运行了一段时间后,因某些原因服务器的数据丢失了,但app端本地还保留着会话列表和消息,如果app端调用deleteConversationAndDeleteAllMsg接口,删除会话记录会提示错误导致无法删除,请问除了卸载APP重装的方法之外,有没有其它方法可以清除app端本地的会话和消息?我看了你们的官方文档(https://docs.openim.io/zh-Hans/sdks/api/conversation/hideAllConversation)有deleteAllConversationFromLocal接口的原型,但是没有找到这个接口
Additional information
No response
The text was updated successfully, but these errors were encountered: