-
-
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
Local CloudCode server URL #131
Comments
This was referenced Feb 1, 2016
Follow on in #132. |
montymxb
pushed a commit
to montymxb/parse-server
that referenced
this issue
Feb 14, 2016
…inWithFacebook_object_creation Use ParseObject::create() to create new ParseUser
This was referenced Jul 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seems like all Parse actions done within Cloud Code are against Parse.com apps and not against local Parse Server. When I started trying out Parse Server I've set all keys to corresponding keys of my Parse.com app. Now I've got 155 error in my trigger, which should not be happening as I don't see anything within parse-server repo to throw it. So looks like it was communicating with Parse.com. When I changed all keys to random string I started getting I/O errors in Android app.
Here is the code in
index.js
:I wasn't able to find any way to provide server url in JS SDK. Am I missing something? Anyway, JS SDK initialized with Parse Server should probably be connected to localhost.
The text was updated successfully, but these errors were encountered: