-
Notifications
You must be signed in to change notification settings - Fork 21
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
callback url #3
Comments
Hi @headwinds, I will check this. Thank you for posting this. Currently I am sick, I caught some cold, but when I get better I will look at this. |
@ivanvs that would be great - get well first! something may have changed since you created this repo or I may have a bug but seeing your callback url would help rule that out. If you could run both the frontend and backend on your machine and confirm the twitter login is still working for you that would help too. I would rather use your approach then resorting to firebase to get social auth |
Any update on this? |
@headwinds @DanDAAllen callback should be http://localhost:3000/twitter-callback |
why should that be?? that's not a route on the front end |
@ivanvs would you like to resolve this call back issue? |
Hi please solve out this issue and i think you are fit now |
Hey. Can you please give an update on this issue? |
In your awesome post you mentioned that callback url is required but you don't show what you entered in the screenshots nor the post.
Can you share that?
I can run both the frontend and backend apps but it fails on the call back url which is required. Since you say it doesn't matter, I thought to simply put:
http://127.0.0.1:4000/
I go through the screen of allowing email in the popup and then this appears:
Then I tried
http://127.0.0.1:3000/
and I got some nice inception happeningI can see the token as a param in that url - but I believe the token should be processed in the backend app not the frontend app. That's why port 4000 should be used....but it's not working.
What did you put as a callback url?
The text was updated successfully, but these errors were encountered: