Failed to persist keys as they are not strings

Description:

When I enabled E2EE and logged into the system, the browser console displayed the error shown in the screenshot. I checked the e2e.fetchMyKeys API, and the response data was:

{"success":true}

There was no public_key or private_key. Then, I checked the users table, and those fields were also missing.

According to the documentation, it is described as follows:

When a user logs in, the client auto-generates an encryption password and prompts the user to save it. This password generates a secure 256-bit AES-CBC encryption key called the “Master Key.” The Master Key is central to encrypting and decrypting the user’s private key.

Upon initial login, the system did not generate the expected private_key and public_key. What might be causing this issue? Are there manual allocation methods available?

Steps to reproduce:

Expected behavior:

Actual behavior:

Server Setup Information:

• Version of Rocket.Chat Server:
• License Type:
• Number of Users:
• Operating System:
• Deployment Method:
• Number of Running Instances:
• DB Replicaset Oplog:
• NodeJS Version:
• MongoDB Version:

Client Setup Information

• Desktop App or Browser Version:
• Operating System:

Additional context

Relevant logs:

No file or test is named in the report. Start by tracing the e2e.fetchMyKeys entry point and the login-time E2EE key-generation flow, then compare the API response with the users table fields; done means generated keys are persisted and returned by the API.