-
-
Notifications
You must be signed in to change notification settings - Fork 595
Parse.User.signUp doesn't pass installationId #536
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
@smassin I don't know if this is still a problem. Maybe you can add a PR with a fix for it. |
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. |
dplewis
added a commit
that referenced
this issue
Dec 11, 2019
Fixes: #536 Parse.User.signUp actually does a ParseObject.save() at its core which does not send an installationId. This is useful to prevent invalid session token and tests session clean up.
davimacedo
pushed a commit
that referenced
this issue
Dec 11, 2019
Fixes: #536 Parse.User.signUp actually does a ParseObject.save() at its core which does not send an installationId. This is useful to prevent invalid session token and tests session clean up.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As the title suggests, using
does not actually pass the installationId.
I spent more time than I probably should tracking down the issue here parse-community/parse-server#3996
The short answer is Parse.User.signUp actually does a ParseObject.save() at its core which does not send an installationId. Inserting the following code just before this line
solves the problem:
Parse-SDK-JS/src/ParseObject.js
Line 1085 in ee33c48
The text was updated successfully, but these errors were encountered: