-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Accounts get disconnected #4471
Comments
/PS: as the Readme says, repo is elsewhere: https://codeberg.org/iNPUTmice/Conversations Anyway, Device ? Android version? Conversations version? Server software & version? Is "channel binding" enabled server side? Enabled in Conversations? Logcat logs of the messages during such times for this account? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I can confirm that an issue similar to #2293 (not sure if the exact same) still happens with recent versions of Conversations. In my case, an account that had not seen use in a long time but was on and successfully staying online, became and stayed offline (as externally visible from status, did not test messaging) for days despite the fact it was set to on (I think Conversations may have falsely showed it as "Online", not "Connecting...", but I'm not 100% sure). The other accounts remained actually online during the time period and worked fine. It was necessary to manually toggle that account off and on, and then it started to work immediately. The version was about a year old, which is far more recent than the date of #2293. I can't re-test with a newer version, this issue doesn't happen often.
Note: The case I am reporting here is totally unrelated to my battery management experiment I mention in another post. In this case, Conversations' service remained on and working at all times.
The text was updated successfully, but these errors were encountered: