Skip to content
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

Error when trying to log in since updting to 2.2.12 #2037

Closed
Kinzi opened this issue Jun 12, 2016 · 7 comments
Closed

Error when trying to log in since updting to 2.2.12 #2037

Kinzi opened this issue Jun 12, 2016 · 7 comments

Comments

@Kinzi
Copy link

Kinzi commented Jun 12, 2016

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"

@kocoai
Copy link

kocoai commented Jun 12, 2016

Me too, parse-server 2.2.12 with SDK iOS:
[Error]: schema mismatch for _Session.user; expected Pointer but got String (Code: 111, Version: 1.13.0)

@ho-shing
Copy link

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

@kocoai
Copy link

kocoai commented Jun 12, 2016

@wilsonths thank you ! => workaround: npm install deepcopy@0.6.1

@Kinzi
Copy link
Author

Kinzi commented Jun 12, 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 deepcopy@0.6.1 in node_modules/parse-server.
The ^0.6.1 in package.json obviously resolves to 0.6.2 ...

@andj207
Copy link

andj207 commented Jun 12, 2016

@wilsonths thank you! you've save my day

@pan83
Copy link

pan83 commented Jun 12, 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.

@drew-gross
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants