RocketChat / RocketChat/Rocket.Chat
[7.7.1] The application GUI just crashed on admin login
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
I have a fresh installation that I started with version 7.6.0 and then updated to 7.7.1. When a user with the admin role logs in, they receive the error: "Application Error - The application GUI just crashed."
If I remove the admin role from the user, they can log in successfully after refreshing the page. But as soon as I reassign the admin role, the same error happens again.
I’ve checked older issues and tried the suggested fixes, but none of them solved the problem:
- The user has empty banners:
banners: {} - The user has empty settings:
settings: {} - The
db.rocketchat_bannercollection is empty - The
Canned_Responses_Enablesetting was deleted
My users are created via OAuth. I was able to log in with an admin user before, but I'm not sure at what point it stopped working.
These tests were done in the browser. On the iOS app, the user is able to log in, but the admin panel keeps loading indefinitely.
Steps to reproduce:
- Assign the admin role to the user.
- Log in with the user who has the admin role.
- Observe the error: "Application Error - The application GUI just crashed."
- Remove the admin role from the user.
- Refresh the page — the user can now log in without error.
- Reassign the admin role to the user.
- Refresh the page again — the error returns.
Expected behavior:
Admin user should login normally.
Actual behavior:
The user cannot login and the message "Application Error - The application GUI just crashed." is displayed.
Server Setup Information:
- Version of Rocket.Chat Server: 7.7.1
- License Type: Community
- Number of Users: 10
- Operating System: Docker image
- Deployment Method: Docker
- Number of Running Instances: 1
- DB Replicaset Oplog: 1 mongo instance on Docker
- NodeJS Version:
- MongoDB Version: 6.0
Client Setup Information
- Desktop App or Browser Version: All browsers (Edge, Chrome, Brave)
- Operating System: Windows
Additional context
Relevant logs:
There is no log output in the server application. The only log I see is from the browser console:
verifyErrors.js:34 Error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at sv (verifyErrors.js:34:1)
at d (verifyErrors.js:34:1)
at m (verifyErrors.js:34:1)
at M (verifyErrors.js:34:1)
at aj (verifyErrors.js:34:1)
at i (verifyErrors.js:34:1)
at si (verifyErrors.js:34:1)
at so (verifyErrors.js:34:1)
at su (verifyErrors.js:34:1)
at i3 (verifyErrors.js:34:1)
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 browser login with an OAuth-created user who has the admin role, then inspect the reported React error and compare the admin and non-admin login paths. The fix is complete when admin users can log in normally in supported browsers without the GUI crash, while non-admin login continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, mongodb, react, typescript
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100