RocketChat / RocketChat/Rocket.Chat

TypeError "c.join is not a function" on outgoing integrations page

Open
#19,586 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

area: ui/ux type: bug
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

Opening the Integrations -> Outgoing tab leads to an empty page with the following error in the console:

/node_modules/react-dom/cjs/react-dom.production.min.js:217 TypeError: c.join is not a function
    at S (/client/admin/integrations/IntegrationsTable.js:1)
    at oh (/node_modules/react-dom/cjs/react-dom.production.min.js:161)
    at Rj (/node_modules/react-dom/cjs/react-dom.production.min.js:269)
    at Qj (/node_modules/react-dom/cjs/react-dom.production.min.js:254)
    at Kj (/node_modules/react-dom/cjs/react-dom.production.min.js:254)
    at yj (/node_modules/react-dom/cjs/react-dom.production.min.js:247)
    at eval (/node_modules/react-dom/cjs/react-dom.production.min.js:131)
    at exports.unstable_runWithPriority (/node_modules/scheduler/cjs/scheduler.production.min.js:27)
    at cg (/node_modules/react-dom/cjs/react-dom.production.min.js:130)
    at fg (/node_modules/react-dom/cjs/react-dom.production.min.js:131)
Steps to reproduce:
  1. Go to the Admin area
  2. Click on Integrations
  3. Click on Outgoing
Expected behavior:

The list of outgoing integrations to show

Actual behavior:

An empty page with the above error in the browser console

Server Setup Information:
  • Version of Rocket.Chat Server: 3.7.1
  • Operating System: Ubuntu 18.04
  • Deployment Method: docker rocketchat/rocket.chat:3.7.1
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: v12.18.4
  • MongoDB Version: 3.6.20
Client Setup Information
  • Desktop App or Browser Version: Safari 14.0.1 / Chrome 87.0.4280.66
  • Operating System: macOS 10.14

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with client/admin/integrations/IntegrationsTable.js, identified in the console stack trace, and reproduce the issue by opening Admin > Integrations > Outgoing. Trace the value causing c.join to fail, then verify that the outgoing integrations list renders without a console error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.