-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Still have issues logging in with anonymous user #1198
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
What is the error that you experience on the Android SDK? |
Android SDK v1.13
|
I guess the bigger question is why all these fields are being sent back on the PUT request:
|
Do you have a beforeSave or an afterSave? Depending on the case, parse-server may return some fields. Given your logs:
There is a PR opened (#1199) but I'm waiting for unit tests from @yuzeh in order to merge to prevent any further regression. |
Yes, I have both a beforeSave and afterSave. The behavior in hosted parse seems to be to not return these fields, so I guess there is an inconsistency here. Probably the Android client should not be treating a Map as a JSONObject either... |
@flovilmart I spent yesterday trying to figure out a test case that would make sense. Now that I understand that beforeSave/afterSave handlers affect what fields get returned, I think I can make that test case. I'll look into it later today. |
I'm opening a new issue to document my ongoing issues with upgrading from anonymous users.
This is related to #1136 and #639.
On the latest release,
authData
is still not properly cleaned on PUT requests for the _User class. See below for VERBOSE=1 logs from a parse-server I've set up. This causes an error on the Android SDK.There are probably two good ways of fixing this:
1ed868b goes part of the way to fixing it server-side, but does not do it everywhere it should.
I'm in the process of putting a pull request that will fix this in
RestWrite.js
handleUpdate
as well ashandleLogIn
inUsersRouter
.For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
Environment Setup
AWS/ElasticBeanstalk, parse-server 2.2.2
Steps to reproduce
It will be hard to give clean repro steps on a general app that has anonymous users enabled, but if requested I'll try.
Logs/Trace
The Android SDK issues a PUT request for signup instead of calling the signUp endpoint because this user already has data saved to the parse-server. The key thing to notice is that in the response, the value associated with
authData
is{"anonymous": null}
instead ofnull
.The text was updated successfully, but these errors were encountered: