-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Problem upgrading from anonymous user #1136
Comments
Thank you for providing detailed request/response logs... We'll take a look asap. |
@lolobosse the PR is in review, a stupidity from my craft... |
Hey @flovilmart, I wanted to try your fix but I somehow failed at it, Maybe to speed up the process, it can be something cool not only to give the instruction to run the server in "prod" mode but also in dev mode (from source), where the people can play with the code. Do you have a Readme How to build from source? because I'm battling against it. What I tried was: I tried If you can give me some directions for that (I'm very bad at configuring but a real pitbull at debugging 😉 🐶 ) Btw how do you handle config file in dev mode? Actually I think to doc is missing for contributing properly when not familiar with NPM and JS in general. |
@lolobosse Usually I don't run from source but rely on unit tests to implement the fixes. I use the VERBOSE=1, debug is tricky as we transpile with Babel and don't build the source maps. |
I succeed, modified the lib code directly, works fine 😉 |
With the PR fix? |
Yes with the PR FIx |
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!
What is the issue?
I recreate an issue but it is related to #639 . Please do not close it yet and let me explain the problem 😄 First the issue is not a problem itself and having
"anonymous": null
is perfectly fine. So I think it makes sense to create an issue which cares about this possible bug (at least @flovilmart marked as bug on the other issue).Environment Setup
VERBOSE=1
Steps to reproduce
That's the biggest issue, it happens only on mobile because it is related to the anonymous feature which has been thought for mobile only. However I succeed to make two flavours of my app (however it is closed source, so I hope we can solve the bug without needing my app yet, I can provide access for further investigations but not to the whole world 😆). One flavour is on the parse.com and the other is running the latest vanilla version of my server.
As you may expect the Parse.com is slower but works perfectly and the bug only concerns Parse-Server.
Logs/Trace
Let's try to debug it without the app; here are the curl and the response from Parse.com (working):
Response:
User is updated, everything fine; then I try to login:
Response, working:
The Parse-server, not working:
Response:
Login:
Response (of course I just call login when I returned from signup):
So I guess the transformation is not done properly in the server but it stills return a successful response.
Another way of seeing it is that the username is not updated in the parse dashboard.
Btw, I hope it can get fixed soon because we're waiting for this to go online 🎉 🎉 😆 🚀 🔥
The text was updated successfully, but these errors were encountered: