Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[4.6.0] Upload emoji/avatars - get Error: "The formData parameter MUST be an instance of the FormData class." #25041

Closed
charisteed28 opened this issue Apr 3, 2022 · 6 comments · Fixed by #25069

Comments

@charisteed28
Copy link

Description:

When you try to upload an avatar or emoji, they don't load.

Steps to reproduce:

For example, emoji:

  1. Go to Administration -> Custom Emoji.
  2. Click new, choose Name, upload image.
  3. Click on save.

Expected behavior:

Emoji/avatars added.

Actual behavior:

Get error:
Error: The formData parameter MUST be an instance of the FormData class.
image

Server Setup Information:

  • Version of Rocket.Chat Server: 4.6.0
  • Operating System: Debian
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: yes
  • NodeJS Version: 14.18.3
  • MongoDB Version: 4.4.12

Client Setup Information

  • Desktop App or Browser Version: Desktop App 3.7.8. Firefox, Chrome.
  • Operating System: Windows 10.

Additional context

Looks like a fixed in 3.6.1 bug:
#18736

Relevant logs:

No logs about this problem.

@artemChernitsov
Copy link

+1

@kitich
Copy link

kitich commented Apr 5, 2022

Same issue

Version
4.6.0
Deployment ID
Zj3rvZHiBavvfDN42
Apps Engine Version
1.31.0
Node Version
v14.18.3
Database Migration
258 (April 2, 2022 9:06 AM)
MongoDB
4.0.20 / mmapv1 (oplog Enabled)
Commit Details
HEAD: (843d7adf7)
Branch: HEAD

@dudanogueira
Copy link
Contributor

Hi! Our team is aware and working on it!

@moell9
Copy link

moell9 commented Apr 12, 2022

This problem is still available in 4.6.1. Can someone reopen this issue please.

@TwizzyDizzy
Copy link

This problem is still available in 4.6.1. Can someone reopen this issue please.

This is not true for me: 4.6.1 fixed the issue in my case.

Cheers
Thomas

@moell9
Copy link

moell9 commented Apr 12, 2022

I row back a little. I just saw that I'm still on 4.6.0.

@tassoevan tassoevan added type: bug and removed bug labels Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants