RocketChat / RocketChat/Rocket.Chat
Cloud Registration Warning showing even though Rocket Default Gateway is disabled.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Big red notice appears at the top stating that "Cloud registration is still pending", but we have the default rocket gateway disabled and are using our own firebase code for push notifications.
Steps to reproduce:
- Open Rocketchat Client
- See the big red warning at the top.
Expected behavior:
This warning should only apply to servers that are using the default rocket gateway.
Actual behavior:
The warning shows even though we are not using the rocket push gateway.
Server Setup Information:
- Version of Rocket.Chat Server: 3.6.2
- Operating System: Debian 10 (Linux)
- Deployment Method: tar
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled
- NodeJS Version: v12.14.0
- MongoDB Version: 4.2.7
Client Setup Information
- Desktop App or Browser Version: 12.17.10
- Operating System: Windows 10
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 in the Rocket.Chat Client's cloud-registration warning and compare its condition with the default Rocket gateway setting and the custom Firebase push configuration. Reproduce the warning with the gateway disabled; done means the warning no longer appears for servers using their own push-notification setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- firebase
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100