-
-
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
Unauthorized Save Object in Cloud Code #13
Comments
Yes we should update the docs for this, when using Parse as a client, you need to update the server address.. Parse.serverURL = "https://....."; |
Ok , I'm running the local server with javascript sdk client perfectly, just not working manipulate objects in local cloud code . I will wait for the update documentation. |
In your case, at the top of the cloud code file, try: Parse.serverURL = 'http://localhost:1337/parse'; |
It's working! thank you. |
@gfosco this can be closed now. |
Adding Parse.serverURL = 'https://fast-badlands-XXX.herokuapp.com/parse' at the top of the cloud/main.js does not work for me. Query in cloud code always return error: unauthorized If I use Parse.Cloud.useMasterKey(); query worked |
Instead of |
I'm using The following is wrapped in a
|
I have to set serverURL AND useMasterKey to make query to work. |
Hi All, I'm also facing similar issue while trying to update the User Object. In console log, I can only see "before save" message and then after couple of seconds it shows error.
In heroku log, it shows Request timeout error.
I'm able to call all other cloud function. Could you assist me here ? Thank you in advance !! |
My issue was related to the 'userMasterKey' requirement. What I didn't understand was the .save() function needs this as a second argument. Guess I need to read the method signatures for every call. |
Hello everyone! I am unable to save an object in cloud code . I arrive in the method, but every time I save is return "code : 141 - unauthorized " . Are there any special permission to cloud code in parse server?
my code:
The text was updated successfully, but these errors were encountered: