Parse-server: Error when trying to log in since updting to 2.2.12

Created on 12 Jun 2016 · 7Comments · Source: parse-community/parse-server

I just upgraded to 2.2.12 locally. Now, when I try to log in using js sdk 1.8.5 and Parse.User.logIn(user, password, response) I get this error:

code: 111, message: "schema mismatch for _Session.user; expected Pointer but got String"

I only updated parse-server and my setup worked perfectly with 2.2.9.

Any ideas?

-EDIT-
With 2.2.10 I get this: code: 111, message: "schema mismatch for _Session.user; expected [object Object] but got String"

Source

Kinzi

Most helpful comment

Looks like the dependency deepcopy 0.6.2 causes the issue. A workaround is to fallback to deepcopy 0.61.

ho-shing on 12 Jun 2016

👍5

All 7 comments

Me too, parse-server 2.2.12 with SDK iOS:

kocoai on 12 Jun 2016

Looks like the dependency deepcopy 0.6.2 causes the issue. A workaround is to fallback to deepcopy 0.61.

ho-shing on 12 Jun 2016

👍5

@wilsonths thank you ! => workaround: npm install [email protected]

kocoai on 12 Jun 2016

Thx @wilsonths
~~didn't work for me - also deepcopy already is 0.6.1 in parse's package.json~~
OK, it does work when overriding deepcopy with npm install [email protected] in node_modules/parse-server.
The ^0.6.1 in package.json obviously resolves to 0.6.2 ...

Kinzi on 12 Jun 2016

@wilsonths thank you! you've save my day

andj207 on 12 Jun 2016

Thank you, it works. To prevent similar problems in the future, may I ask how can we pin all the currently used dependency packages to ensure that we can rollback to a well tested deployment? We are using the parse-server-example project for our deployment on heroku.