zackad opened this issue a year ago · 2 comments
This error seems caused by #199 and give wrong error message. Can't reproduce the error on dev environment.
Only happen on production environment. Require proper logging for error tracing.