Accessing the Parse server in Android without a master key doesn't give authorization -

when access server following works:

curl -x post \   -h "x-parse-application-id: xxx" \   -h "x-parse-master-key: yyy" \   -h "content-type: text/plain" \   -d '{"score":1337,"playername":"sean plott","cheatmode":false}' \   http://xx.xx.xx.xx/parse/classes/inventory 

but when use following, doesn't:

curl -x post \   -h "x-parse-application-id: xxx" \   -h "content-type: text/plain" \   -d '{"score":1337,"playername":"sean plott","cheatmode":false}' \   http://xx.xx.xx.xx/parse/classes/inventory 

i error instead:

{"error":"unauthorized"} 

it worked fine earlier. had changed few settings , updated latest parse server version , stopped working, along other apps related it.

the web version works, suggesting rest api key fine. can access through dashboard too. problem when access android, can give application id identification.

might have changed setting wrong blocked this? don't think changed anything, though there small possibility didn't close bracket or commented out on server.js file.

it's brought here: https://github.com/parse-community/parse-server

the client keys used parse no longer necessary parse server. if wish still require them, perhaps able refuse access older clients, can set keys @ initialization time. setting of these keys require requests provide 1 of configured keys.

• clientkey
• javascriptkey
• restapikey
• dotnetkey

what happened had restapikey inside config file, required 1 of other 4 keys well. new update forced app use clientkey or remove restapikey config.