[BUG] How to Keep the online stattus for the Client
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 159
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
OpenIM Server Version
3.8.3
Operating System and CPU Architecture
Linux (AMD)
Deployment Method
Source Code Deployment
Bug Description and Steps to Reproduce
After deployment, Everything seem to OK, The andriod clinet work normal.
But several hours later, client A can't call client B online, the status of the clientB seems is online, But have to relogin to work.
Screenshots Link
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by reproducing the stale online-status behavior in the 3.8.3 source deployment with an Android client, then trace how server and client presence changes after several hours. Done means client B remains callable while shown online without requiring a relogin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, go, linux
- Domain
- backend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100