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
Message loss #4470
Comments
Accounts, account, upper right menu, Archiving, is set to Always? You sure? Server has Carbons? Any logs from logcat? You can repro this at will? Eg. Kill app, send message, no message arrives? /PS: the actual repo is elsewhere, https://codeberg.org/iNPUTmice/Conversations as the Readme says... |
Yup.
Yep.
Did not check logs, I expect they may have been deleted by now and I cannot test further due to see below.
From all the testing I performed, the message loss seems to occur immediately when Conversations is unexpectedly shut down, in this case from battery management. It is something that consistently occurred, 100% of the time during the small period of time this circumstance was happening. This doesn't seem to need further testing given that the Conversations documentation itself notes that this may happen -- a behavior that I consider improvable, given the reasons in my initial post. I would expect it to also happen from other unexpected shutdown causes, but did not test that. I don't want to bother with further testing bc I don't have a test device and do not want to interfere with my normal Conversations usage. |
If this happens daily, surely logcat will have it, you can expand the log size in Developer options, iirc |
The message loss text might be there since 2014 for all I care, these are rarely if ever an occurence. |
Recently, I turned on the battery management features on my device and noticed I was losing some messages. I later found that Conversations states:
"Your device is employing heavy battery optimizations ... which may lead to delayed notifications or even message loss"
Ignore the delayed notifications, which are expected. The fact that the message loss part occurs seems to be improvable on Conversations' part:
The text was updated successfully, but these errors were encountered: