Parse.User.login don't work as expected

[omar-bz]

Hi I'm using "parse": "^1.9.2".
the problem is present when trying to login with invalid user, it generate an error.
when using:
Parse.User.logIn(email,pass,{success:u=>do_some_stuff(u),error:e=>show_the_error_message(e)})
an error is loged to the console and the error function is fired:

but when using the promises:
Parse.User.logIn(email,pass).then(u=>do_some_stuff(u)).catch(e=>show_the_error_message(e))
it only log the error on the console and do not resolve or reject the promise.
How this is happening and to fix it.
edit:

Parse.User.logIn instead of Parse.logIn

[wesliel]

According to JS SDK, Parse object doesn't have logIn method, it belongs to Parse.User. Does it work if it invokes Parse.User.logIn() instead?

[natanrolnik]

@wesliel is correct. Please see the docs on Parse.User.login(): http://parseplatform.org/Parse-SDK-JS/api/classes/Parse.User.html#methods_logIn

Additionally, you are handling the error from the promise incorrectly. Parse.Promise differs from the other JS promise implementations:
http://parseplatform.org/Parse-SDK-JS/api/classes/Parse.Promise.html

[omar-bz]

i mean Parse.User.LogIn but it is typing fault, if i really test it with Parse.Login it will not execute it will through an error immediately and do not produce the output i'm showing.
And why you close the issue this does not resolve the first part it still log 404 not found.

[flovilmart]

Are you passing the email and not the username?

[omar-bz]

the email is the username they are equal.

[flovilmart]

Can you try with the latest version 1.10.1 and let us know if it’s the same?

[omar-bz]

I try the 1.10.1 version with new projects using nextjs and using reactjs alone and using:
node v6.9.2, npm 3.10.9 (i dont know if it is important). but it still log that error 404 not found even when i do not log anything, i used this code:

Parse.initialize('appId');
Parse.serverURL = 'serverUrl';
Parse.User.logIn('random email', 'random password', {
  success: user => {
    console.log(user);
  },
  error: (user, error) => {
    console.log(user, error);
  },
});

[natanrolnik]

@bouzoumita which parse-server version are you using? And when did this bug started happening?

[omar-bz]

i was using the version 2.6.3 of parse server, now I upgrade to 2.6.5 but still get same thing.

[natanrolnik]

And if you try using the Rest API, do you get the same error? If so, then it’s a bug in Parse Server.

[flovilmart]

@bouzoumita can you provide the server logs when running with VERBOSE=1 please?

[omar-bz]

@flovilmart edit this is the log in relation with the problem in the server:

�[31merror�[39m: Error generating response. ParseError { code: 101, message: 'Invalid username/password.' } code=101, message=Invalid username/password.
�[31merror�[39m: Invalid username/password. code=101, message=Invalid username/password.

and this after activating the verbose:

�[36mverbose�[39m: REQUEST for [GET] /parse/login: {
  "username": "randomInvalidemail",
  "password": "********"
} method=GET, url=/parse/login, host=MYDOMAIN.com, x-real-ip=MYIP, x-forwarded-for=172.31.35.209, connection=upgrade, content-length=282, pragma=no-cache, cache-control=no-cache, origin=http://localhost:3000, user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36, content-type=text/plain, accept=*/*, referer=http://localhost:3000/try, accept-encoding=gzip, deflate, br, accept-language=en-US,en;q=0.8,fr;q=0.6,ja;q=0.4, username=randomInvalidemail, password=********
�[31merror�[39m: Error generating response. ParseError { code: 101, message: 'Invalid username/password.' } code=101, message=Invalid username/password.
�[31merror�[39m: Invalid username/password. code=101, message=Invalid username/password.

@natanrolnik the problem is visible only in the browser , with parse/node it fire the error callback only

[fchu]

Any update? I'm still seeing the issue with parse@^1.11.1

FWIW it shouldn't matter if Parse server is working properly or not, any kind of error as seen by the client should be captured by the promise (instead of being seen in the console)