New emoji is added.
Get the err: The formData parameter MUST be an instance of the FormData class.
No Log entry on the Server
I was just about to write a report on this.
As far as I could gather information, it broke during the transition from version 3.5.3 to 3.5.4
Hi!
I have the same problem. Changing avatar worked fine in 3.5.3, and this error started after updated to 3.6.0.
New comers to Rocket.Chat, fresh install on 3.6, same problem.
Same here, 3.6.0
the same case in 3.6.0
the same case in 3.6.0
Also happening with me in 3.6.0 for profile avatar.
Didn't tested with emojis.
same here
same here, fresh 3.6.0, can't upload avatar, url method works well
Same here Version 3.6.0
Try to change Profile avatar I get the error message "The formData parameter MUSTbe an instance of the FormData class."
If I try to change the avatar of a channel, the "hide system message" option is reset.
And I get the following message in the error log: Exception in setTimeout callback: TypeError: Cannot read property 'etag' of undefined at app/lib/server/functions/setRoomAvatar.js:34:46 at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1234:12) at packages/meteor.js:550:25 at runWithEnvironment (packages/meteor.js:1286:24)
Need urgent a solution to fix it
Same here, upload not working, can only use avatar via url
Another case here, I just updated to the latest release and some users reported me this case.
Same problem here.
Can't add a custom emoji (although ones already added work).
Tried .gif and .png
(Tried Chrome & Edge as well)
Version: 3.6.0
OS: Linux (3.10.105) (Official Docker Container)
Node Version: v12.16.1
MongoDB Version: 4.4.0 (wiredTiger)
Over a week and no dev comments?
me same problem
same here
Is there any solution or workaround available for this issue? We are also facing this same issue with latest installation of rocketchat version 3.6
Same here with develop e30af61.
Is there any solution or workaround available for this issue? We are also facing this same issue with latest installation of rocketchat version 3.6
There hasn't been _any_ dev acknowledgement of this issue.
Same Problem here would be cool if a Dev could take a look at it.
The same issue appears here, I have two different instance running..one is a docker-container mode (one container running behind a web-proxy) and a two-instance nodes running behind nat ,both version 3.6.0 . the cluster-mode one (docker-container) has the same issue :(
This only seems to effect User Avatars, I successfully managed to change a Channel Image.
@nstoeckigt , it also affects custom emoji.
No dev comments yet. I'm just including myself in here because there hasn't been no note and issues keep piling up. I'm trying to be nice by being patient. So hopefully they'll be able to fix this, else im gonna have to recreate my docker image and go back to 3.5.3 which isn't bad.
I'm just upgraded to 3.6.0 and experienced same issue. No way to change user avatar, except changing image physically on disk.
Sorry folks, for the lack of response. We just opened a PR to address this, which will be probably shipped with the next patch release, 3.6.1.
Sorry folks, for the lack of response. We just opened a PR to address this, which will be probably shipped with the next patch release, 3.6.1.
Thanks for the fix :)
I think people are feeling a bit too entitled around here - you're all doing a great job. Personally, I'm very grateful :D
Sorry folks, for the lack of response. We just opened a PR to address this, which will be probably shipped with the next patch release, 3.6.1.
Thank yo very much, this fix is very appreciated. When does the release of 3.6.1 is aimed at?
@Atomzwieback It should land today or tomorrow I think 馃
Awesome, glad to hear this being addressed!
@Atomzwieback It should land today or tomorrow I think 馃
Docker container release should be shortly after the normal release right?
Docker container release should be shortly after the normal release right?
Yes, those are built automatically whenever theres a new release appearing in the GitHub releases section.
Sorry folks, for the lack of response. We just opened a PR to address this, which will be probably shipped with the next patch release, 3.6.1.
Great news, Jonas!
And please don't forget to prepare bug fixes for that bugs (I think part of them could be fix by https://github.com/RocketChat/Rocket.Chat/pull/18841)
https://github.com/RocketChat/Rocket.Chat/issues/18831 and https://github.com/RocketChat/Rocket.Chat/issues/18737
https://github.com/RocketChat/Rocket.Chat/issues/18829 and https://github.com/RocketChat/Rocket.Chat/issues/18740
Thank you to the devs personally from the bottom of my heart. I hope you guys been okay. You are awesome in your own right. thank you so much for maintaining this beautiful chat. :) 馃挴 鉂わ笍 馃憤馃徎 馃槑
Can confirm on 3.5.3.
I'm still seeing this error in 3.6.0.
@NineBAR It was reported in 3.6.0. It is supposedly fixed for 3.6.1 (obviously will confirm once it's released).
@NineBAR It was reported in 3.6.0. It is supposedly fixed for 3.6.1 (obviously will confirm once it's released).
My mistake. Thanks!
Most helpful comment
Sorry folks, for the lack of response. We just opened a PR to address this, which will be probably shipped with the next patch release, 3.6.1.