Parse.User.save() does not work in parse@3.5.0

[dipendras]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the version 4.5.0 of Parse Server and the latest version of Parse JS SDK.

Issue Description

Parse.User.save() does not work in parse@3.5.0

Steps to reproduce

let user = new Parse.User();
user.set("username", "xx");
user.set("email", "xx@xx.xx");
user.set("password", "xx");
saveduser = await user.save();

Actual Outcome

It is saved/updated in the local session but not in the backend/server.

Expected Outcome

Update the data in the backend/server.

Environment

Server

• Parse Server version: 4.5.0
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Back4app

Client

• Parse JS SDK version: 3.5.0

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

I can reproduce the issue with the version 4.5.0 of Parse Server

Can you reproduce this issue with the latest alpha version of Parse Server 5?

[MarcDerhammer]

I believe this also applies to
Parse.User.signUp

When calling this, it is not sending any network request.
Downgrading to 3.4.4 resolves it for me.

logIn is fine

[mtrezza]

Which Parse Sever version did you use?

[MarcDerhammer]

I was on server 5.2.4, but bumping up to 5.3.0 did not resolve it.

const signUp = async (username, password) => {
    try {
        const user = new Parse.User();
        user.set("username", username);
        user.set("email", username);
        user.set("password", password);
        await user.signUp();
    } catch (error) {
        alert(error.message);
    }
}

the above code works well on JS SDK 3.4.4 but not 3.5.0.

Watching the network tab on developer tools shows no request when calling signUp

maybe worth noting I'm pulling it from this CDN

[mtrezza]

The CI for release branch indeed shows that there are some tests failing:
https://github.com/parse-community/Parse-SDK-JS/actions/runs/3373095961/jobs/5649179081

Looking at the badges, the alpha and beta branches build successfully, only the release branch is failing:

Could you try with the latest alpha and beta version of the Parse JS SDK?

[mtrezza]

@MarcDerhammer Is there no log output at all when this fails? Could you try this in a local environment and run the integration test for signup? I assume there is one.

[aarondill]

upon further investigation, my previous comment seems irrelevant, due to the different causes of the issues.

I will leave this issue with a comment pointing out the only changes between the User.save() functions shown in v3.4.4 and v3.5.0:

In v3.4.4:

return _regenerator.default.wrap(function (_context2) {...})

in v3.5.0:

return _regeneratorRuntime().wrap(function (_context2) {...})

the contents of the two functions are identical. the only difference is the call to _regenerator.default.wrap versus _regeneratorRuntime().wrap.

As I don't understand what the code does in each case, I will leave this here for more knowledgeable people. I wish you luck.

[parseplatformorg]

🎉 This change has been released in version 3.5.1-alpha.2

[mtrezza]

Closing via #1600

[mtrezza]

This should be fixed with https://github.com/parse-community/Parse-SDK-JS/releases/tag/3.5.1-alpha.2, could you try it out and let us know?

[MarcDerhammer]

Just confirmed using 3.5.1-alpha.2 resolved the Parse.User.signUp problem I was having.

Thank you very much!

[dipendras]

I confirm that the issue is fixed with parse@3.5.1-alpha.2.

[livingstonef]

I am not sure what i am doing wrong here, but for me Parse.User.signUp in parse@3.5.1-alpha.2 is still not sending any request to the server. Parse.User.logIn works well though.

This is using Parse server version 6.0.0-alpha.9

[mtrezza]

Since the original issue has been solved for others, it may be a different issue. Did you ensure the dependency installed is parse@3.5.1-alpha.2, not just in package.json?

[livingstonef]

Thank you for the reply. I am confident I was using 3.5.1-alpha.2

Anyways. The issue is now gone when using 4.0.0.alpha.3. Thanks again.

[mtrezza]

Thanks for reporting back.

[parseplatformorg]

🎉 This change has been released in version 3.5.1-beta.2

[parseplatformorg]

🎉 This change has been released in version 3.5.1