-
Notifications
You must be signed in to change notification settings - Fork 91
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
Delete message on server will remain in the IOS App #856
Comments
Hey @HuguesDug, |
Hello, Yes, your remark is correct : directly removing from database without going throught the API. Though, Android App or Web version do a resync of the cache when you open the App or open a conversation, what, in my perspective, makes fully sense. In this way, you perfectly warranty the data on the device. Just relying on the local cache leave alive any "problem" that has occured regarding sync or processing messages. I discovered this as I implemented a TTL on read messages with a script that runs on the my sql database. |
So if TTL is something you want to use, there will be support for it in an upcoming version, see nextcloud/spreed#7359 There's also some discussion about lifiting the 6h limit for message deletion, you can find the discussion at
Well, indeed the behavior is different, but it isn't wrong either. The web part of talk only caches messages in the current session, so reloading the page, will reload the messages. On Android there's no offline support, so there's no real caching (never used the android app, just judging from the tickets. There's offline support planned at some point, though: |
I fear the TTL will not suite my need. I want to delete only read messages after a period, unread can stay on the server for unlimited period of time. As far as I could read from TTL concept, all the messages will expire after a period of time, being read of not. Any hint ? |
Not really. What you're trying to achieve is not possible in the current implementation and I don't think that this will change (just my personal opinion). I also can see some problems: What happens if your users turn off read receipts in talk? Suddenly all messages are marked as read and will vanish?! Without knowing the details of your use case, I still think TTL will be the closest you can get at this moment. |
As discussed with @Ivansss there are no plans to change the current behaviour. |
Steps to reproduce
Expected behaviour
When reopening the app, or reopening a conversation, history of the chat messages should be updated, so deleted/modified messages on server side are removed. In the IOS version, the local cache is used and not checked against actual server data.
It works correctly on the web client and on the Android chat client. When a conversation is opened (or app relauched), the local cache is cleared and updated with current server data. A modified or deleted message appear as it should.
Actual behaviour
A none existing message is still shown, where it should not.
Device information
Device: iPhone 6
iOS version: 12
Talk version: All released until the most recent one.
Server information
Nextcloud version: 24.0.3 (but was the same on previous versions). It works on Android and web versions. It is related to startup management in the android App.
Talk version: 14.0.3
Custom Signaling server configured: not relevant,
Custom TURN server configured: yes
Custom STUN server configured: yes
Server log (data/nextcloud.log)
The text was updated successfully, but these errors were encountered: