RocketChat / RocketChat/Rocket.Chat
Desktop App Interface Broken after updating server to 3.14.0
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Upon logging into my self hosted rocketchat instance, I am met with a blank grey screen.
This happens on the desktop app.
Steps to reproduce:
Access Rocket.Chat from the desktop app.
Expected behavior:
I have access to the chat interface.
Actual behavior:
From the desktop app, I see:

With the following errors in the dev console

Server Setup Information:
➔ +-----------------------------------------------------------+
➔ | SERVER RUNNING |
➔ +-----------------------------------------------------------+
➔ | |
➔ | Rocket.Chat Version: 3.14.0 |
➔ | NodeJS Version: 12.22.1 - x64 |
➔ | MongoDB Version: 4.0.24 |
➔ | MongoDB Engine: mmapv1 |
➔ | Platform: linux |
➔ | Process Port: 3000 |
➔ | Site URL: https://<redacted> |
➔ | ReplicaSet OpLog: Enabled |
➔ | Commit Hash: 1255c8f0ca |
➔ | Commit Branch: HEAD |
➔ | |
➔ +-----------------------------------------------------------+
Server is running in a docker container, running on a virtual machine of Ubuntu Server 18.04.5 LTS
Docker version 20.10.2, build 20.10.2-0ubuntu1~18.04.2
Client Setup Information
- Desktop App version: 3.1.1
- Operating System: Pop!_OS

Relevant logs:
Client: 
The server logs do not seem to be relevant, but this is the output from docker logs <rocketchat container>
(node:8) [DEP0131] DeprecationWarning: The legacy HTTP parser is deprecated.
LocalStore: store created at
LocalStore: store created at
LocalStore: store created at
Setting default file store to GridFS
{"line":"120","file":"migrations.js","message":"Migrations: Not migrating, already at version 222","time":{"$date":1619823509288},"level":"info"}
ufs: temp directory created at "/tmp/ufs"
Using GridFS for custom sounds storage
Using GridFS for custom emoji storage
Loaded the Apps Framework and loaded a total of 4 Apps!
Updating process.env.MAIL_URL
➔ System ➔ startup
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
The payload names no files, tests, or code entry points; start with the desktop app developer-console errors and the supplied Rocket.Chat 3.14.0/server and Desktop 3.1.1/client details. Reproduce the login flow using those versions and compare the client and server logs. Done means the desktop app loads the chat interface instead of showing a blank grey screen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100