E2E users cannot reset/reenable 1:1 direct messages, got React minified error on client side

Description:

users cannot reenable e2e in direct messages, all clients are cleaned (no client side data), setting is globally disabled/enabled through admin backend - nothing works - the users get a blank page if they try to enable the e2e in the direct messages (screenshot 1)

i guess have to fix that in mongo db schema to clearly remove all old missconfigurations , but where ?

if u need more informations / logs - no problem - i will paste it if needed ...

Steps to reproduce:

1. reset all clients e2e password in user profile reset e2e
2. try: renable e2e setting globally through admin
3. try: clear message history (old messages are not necesseary, just want clear all)

Expected behavior:

users can wipe their client keys easyli and reenable their 1:1 e2e communications
message history can be lost ... no problem (beta)

Actual behavior:

users got a blank page if they click on enable e2e see screenshots:

url:
https://chat.example.com/direct/aBarMP232NE9EgBc5xFzxzPiMhpMfdCNiL/e2e

screenshot see below 1-5 (Additional context)

users can only fix it with removing /e2e suffix in url path to reenter their the site

Server Setup Information:

• Version of Rocket.Chat Server: 3.10.0
• Operating System: ubuntu 18.04
• Deployment Method: docker
• Number of Running Instances: 1
• DB Replicaset Oplog: 1
• NodeJS Version: v12.18.4
• MongoDB Version: 4.0.21

Client Setup Information

• Desktop App or Browser Version:
  browser:

Google Chrome 87.0.4280.88
Mozilla Firefox 84.0.1

• Operating System:
  ubuntu 18.04

Additional context

screenshots:

1. users try to enable e2e in 1:1 direct messages

2. users got blank page with console client error: (react minified)

3. users reset revoke all their client keys over profile menu

4. users tried to clear , reset their local storage (clear site data , clear local session storage db where the priv/pub keys are stored

5. admin tries to disable / enable e2e globally to revoke all missconfigurations

Relevant logs:

Start at the direct-message /e2e entry point and reproduce the reset and re-enable steps described in the issue, checking the client console for the React error. Trace the blank-page failure and verify that users can re-enable 1:1 E2E messaging without removing /e2e from the URL.