mirror of
https://github.com/nextcloud/talk-android
synced 2025-06-21 12:39:58 +01:00
4a0b67ee9c
It could happen that when sending a message it was received on server but if the servers response is not received, the retry was triggered in the talk app. This sometimes happened when internet connection was not the best. Best would be that messages with the same referenceId would be refused on server side, but this won't be the case for now. So messages with the same referenceId are NOT refused as this would be too much overhead as there would be additional queries on server for every received message) For now, the automatic retry logic is just removed so duplicated messages won't be created automatically. However it's still possible to manually trigger the retry via button. In this case it is not guaranteed that there won't be duplicates. Signed-off-by: Marcel Hibbe <dev@mhibbe.de> |
||
|---|---|---|
| .. | ||
| schemas/com.nextcloud.talk.data.source.local.TalkDatabase | ||
| src | ||
| build.gradle | ||
| lint.xml | ||
| proguard-rules.pro | ||