-
Notifications
You must be signed in to change notification settings - Fork 2
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
Parse sandbox doesn't seem to work #26
Comments
Yes, it's supposed to work the same as the prod one, with the difference that data should go away after some time. I have never tried to use it, but it was part of the specs. |
OK, I think they did not finish this part. Not sure how to do to make data go away after some time, but we could at least try to make it work the same way as the main Parse api. |
ah... it should be finished. It was part of the contract. There's no info about it in the doc? |
Ah yes, I didn't see that I needed also to change the |
cool! close the issue if you think it's solved :) |
I checked further and I was able to get a session id but after I wasn't able to interact with the API. It seems the cloud code is not correctly registered.
I get:
But with the sandbox Parse API:
I get:
Maybe I am still missing something but I rather think it is really not working... |
The problem was that the way to register the cloud functions evolved for the tests but the sandbox API is not included in the tests so they forgot to make the update for the sandbox. I would have liked to include the sandbox in the tests but it does not seem possible to run several Parse servers with cloud code on the same node instance (parse-community/parse-server#116). As the tests create their own connect server instance, for the moment I don't see a solution to run the sandbox in the tests... |
When trying to connect to Parse sandbox with
I get the response
{"error":"unauthorized"}
. Not sure the Parse sandbox has already been working since there is no test for it.@r03ert0: Is it supposed to work the same way as the main Parse api? What should we do with this?
The text was updated successfully, but these errors were encountered: