-
-
Notifications
You must be signed in to change notification settings - Fork 206
signUp returns {"error":"unauthorized"} #79
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
Comments
Ok, I figured it out. In my docker-compose.yaml, I did this:
So, it included the ' before and after app. When I made the header like this, it worked:
Purely my stupidity. |
Hey Rick
I'm not actually sure to be honest.
So, your setup looks correct locally, and your external IP is telling you
that your hitting Parse server... Have you tried maybe tests Ng with your
master/client key and testing if you gain access with that?
I'm not a Parse expert but I have a similar setup using Bitnami images.
Cheers
…On Sun, Feb 10, 2019, 23:55 Rick Spencer ***@***.*** wrote:
Hi. I'm new to Parse. I started with adding signUp functionality, but I
got stuck, and I am hoping you can help me.
I am running parse locally via docker-compose.
These two work:
$ curl -X POST -H "X-Parse-Application-Id: 'app'" -H "Content-Type: application/json" --data ***@***.***"}' http://127.0.0.1/parse/users
$ curl -X POST -H "X-Parse-Application-Id: 'app'" -H "Content-Type: application/json" --data ***@***.***"}' http://127.0.0.1/parse/classes/_User
Here is my code:
Parse().initialize("app", "http://10.0.2.2/parse", debug: true);
ParseUser user = ParseUser("testUser",
"asfasfasfd", ***@***.***");
ParseResponse response = await user.signUp();
Note the different ip address due to running from the emulator. I always
receive:
{"error":"unauthorized"}
from these requests. I have spent a few hours debugging, but I just can't
figure out where the problem is.
I suspect that there is something fundamental about Parse or running from
an emulator that I am not understanding. Any help would be appreciated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#79>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHgn3snZX5a_aaqvy8qd1lWsry6FqnPcks5vMLGDgaJpZM4azW5_>
.
|
@phillwiggins Hi, I guess you missed my comment, but the problem seems to be totally my own silliness. I named the app_id literally "'app'" (with the single quotes).So I wasn't passing the correct app_id in the header,. Thanks for taking a look though. Now that I have this figured out, I should be able to make progress again. |
Hi. I'm new to Parse. I started with adding signUp functionality, but I got stuck, and I am hoping you can help me.
I am running parse locally via docker-compose.
These two work:
Here is my code:
Note the different ip address due to running from the emulator. I always receive:
from these requests. I have spent a few hours debugging, but I just can't figure out where the problem is.
I suspect that there is something fundamental about Parse or running from an emulator that I am not understanding. Any help would be appreciated.
Here is the Parse configuration:
Note that I have redirection port 80 to 1337.
The text was updated successfully, but these errors were encountered: