-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Parse-Server shuts down once a User signup request is received #5192
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
Comments
Can you provide the server logs when running with VERBOSE=1 set? |
nothing output, just shutdown |
Are your running with the verbose logs? What is your configuration? |
`[13728] parse-server running on http://localhost:1337/parse E:\Projects\devdocBack>` |
in verbose mode, just output the request with data and headers, and then the server quits |
What is the exit code of the process? What version of node are you running? |
no exit code |
I just installed the parse-server@3.1.1 using npm instead of yarn. It succeeds with user creation. |
this should make no difference, unless you had different versions of node. |
i don't know why. Since parse-server required node-gyp to compile, and i think there might be differences between npm and yarn in the way they do the compilation. |
We do not test with yarn nor support it actively. |
Issue Description
I was trying to sign up a user to the parse server, and the server shuts down, claiming JSON syntax error. I remove the parse-server@3.1.1 and install an earlier version, 3.0.0. Then used the same piece of data for user creation. You know what, the signup succeeds.
Steps to reproduce
After installing parse-server@3.1.1/3.1.0, and fire a curl command from the rest api doc. The parse server always shuts down.
After installing parse-server@3.0.0, and fire the same command, the parse server accepts the user creation request like always.
Expected Results
User signup succeeds when using 3.1.0 and above versions
Actual Outcome
User signup succeeds when 3.0.0 is in use, but fails 3.1.0 and above versions are in use.
Environment Setup
Server
Database
Logs/Trace
"ParseError: 100 XMLHttpRequest failed: "SyntaxError: Unexpected end of JSON input""
The text was updated successfully, but these errors were encountered: