-
-
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
I'm getting "code":105,"error":"invalid key name:" when I do a POST in my server! #1641
Comments
What version of Please refer to this issue for an example of a great bug report. Make sure these boxes are checked before submitting another issue -- thanks for reporting issues back to Parse Server!
|
@hramos I'm running 2.2.7 and I have all the prerequisites. Also I search many existing issues but I can't resolve this issue. |
@hramos this is an example of my error: verbose: POST /parse/classes/watchlist { 'x-real-ip': 'xxxxxxx', |
Which version of the android SDK are you using, and what calls are you doing to make this request? |
@drew-gross I use Fuse to make apps (https://www.fusetools.com). Fuse use this SDK:
And I use C# to make the HTTP request like this (this is converted to Java in the backend): HttpMessageHandler AddToWatchL = new HttpMessageHandler(); |
It looks like you are using the REST API, not the android SDK, and sending an invalid value. Did this work on api.parse.com? Can you try changing your code to submit the value that you said was working? |
Don't escape the key names inside your This does not seem to be a Parse Server issue, as the server responds successfully when provided with a proper JSON payload (see original post). |
@hramos What do you mean by @drew-gross Yes, this work on api.parse.com. I have my app online with the same code and work perfect.... |
Sorry my mistake! I was doing the HTTP request with |
I really need help to implement a fix that solve my problem (similar to #68). I saw that in #105 there is a fix but in my parse-server I don't have any file called
classes.js
. How can I implement this?Like @mkpazon say:
The problem seems to be due to JSON handling.
The client sends the following JSON in the body
{"where":"{"status":200,"user":{"__type":"Pointer","className":"_User","objectId":"F2ozm6Hgew"}}","count":"1","_method":"GET"}
but the parse-server returns an error.
Changing the above JSON to the following is successful
{"where": {"status":200,"user":{"__type":"Pointer","className":"_User","objectId":"F2ozm6Hgew"}},"count":"1","_method":"GET"}
The text was updated successfully, but these errors were encountered: