RocketChat / RocketChat/Rocket.Chat
Mobile Push still sent after "Logout From Other Logged In Locations"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
When you use "Logout From Other Logged In Locations" button in desktop/web client user is logout from all clients. But despite of logout from mobile client, push notifications still sent. Probably push token is not removed from server.
Steps to reproduce:
- Login in mobile app
- On web/desktop client use "Logout From Other Logged In Locations"
- User logout from all clients
- User still receive mobile push notifications
Expected behavior:
Mobile push notifications not sent after "Logout From Other Logged In Locations"
Actual behavior:
"Logout From Other Logged In Locations" do not stop mobile push sent.
Server Setup Information:
- Version of Rocket.Chat Server: 4.3.3
- Operating System: Centos7
- Deployment Method: docker-compose
- Number of Running Instances: 33
- DB Replicaset Oplog: YES
- NodeJS Version: v12.22.8
- MongoDB Version: 4.2.19
Client Setup Information
- Desktop App or Browser Version: all
- Operating System: all
Additional context
Relevant logs:
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
Start by reproducing the logout flow from the web or desktop client with a logged-in mobile client, then trace how "Logout From Other Logged In Locations" invalidates sessions and how mobile push tokens are handled. Done means that logging out other locations also prevents subsequent mobile push notifications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, node.js, typescript
- Domain
- authentication, backend, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100