Open pehlert opened 4 years ago
Just a quick update, this still happens on 3.4.0 so we are forced to leave the App Framework disabled. I suppose it's something related to our database as nobody has reported it before?
We've run into a similar error log. The problem was that we were saving python uuid type into custom fields. After converting that type to string the error was gone.
Thanks for the insight @MiStr1 - we're not doing that, at least not intentionally. Chances are however that the Giphy app did it at some point. Could you point out what collection caused the issues for you?
The only problem was our python script. In which we were saving data to rocket chat room custom fields. And as I stated before the problem was with the unsuported type being saved in rocket chat custom fields.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This is still happening for us on 3.7.0 when we enable the App Framework. We use LDAP auth, but that's it - everything else is a plain RocketChat installed with all Apps uninstalled now.
Description:
Suddenly our Rocket.Chat instance stopped working and returned TypeError responses to users. We had updated to 3.0.2 about 4 days earlier and it was working stable since then. We were not able to identify any event that led to this behaviour. A restart did not fix it.
As it seems to be related to the App Framework, we tried to disable our only extension "Giphy" at first. This did not solved the issue, except the user saw the
Type Error
responses directly now and not as a reply from rocket.cat.Eventually disabling the App Framework altogether in the "General" tab under "Apps" fixed the issue for us.
We love RocketChat and are happy to investigate further. Thanks!
Expected behavior:
Messages are sent
Actual behavior:
The user gets a Type Error back from rocket.cat:
Server Setup Information:
Client Setup Information
Happens on web and mobile clients
Relevant logs: