openimsdk / openim-sdk-core

Instant Messaging
https://openim.io
Apache License 2.0
340 stars 310 forks source link

Bug: deleteMessageFromLocalStorage interfaces have no effect #530

Open QiuXiaochun opened 5 months ago

QiuXiaochun commented 5 months ago

What happened?

When we call 'deleteMessageFromLocalStorage interface without effect

What did you expect to happen?

To achieve the effect described in the document, after deletion, the deleted message will not appear again unless the application is uninstalled and reinstalled

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

Call the interface, delete a message, re-enter the session, UI again shows the message just deleted

Anything else we need to know?

No response

version

openim-ios-sdk V3.5.1, open-ios-demo V3.4.0

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

cubxxw commented 5 months ago

Could you please provide a detailed description of the specifics?

QiuXiaochun commented 5 months ago

Could you please provide a detailed description of the specifics?

The specific case is that calling this interface does not work, use any of your end demo, and replace the interface that deleted the message with this interface. In theory, if I don't uninstall and reinstall the app, the deleted messages will no longer be visible. In fact, you can see these deleted messages every time you open a session to view a message.

kubbot commented 3 months ago

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 commented 3 months ago

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

FGadvancer commented 4 days ago

Thank you very much for bringing up the issue. This has already been fixed in the issue #683 #669 and will be released in the 3.8.1 (3.8 branch). If you need us to update this fix to a specific branch, please feel free to contact us again, and we will cherry-pick it to the 3.5 branch.