Skip to content
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

Tinderauth failed: Server returned status code 404 #7

Open
alexmoreno opened this issue Nov 8, 2016 · 5 comments
Open

Tinderauth failed: Server returned status code 404 #7

alexmoreno opened this issue Nov 8, 2016 · 5 comments

Comments

@alexmoreno
Copy link

alexmoreno commented Nov 8, 2016

Tinderauth failed: Server returned status code 404 from https://www.facebook.com/intern/common/referer_frame.php

My email and password are correct. Why it's happening?

@thiaguerd
Copy link

i have same problem here

@baskervald
Copy link

Same here, which is a shame because I needed to update my bio and have no access to my phone right now (and tinder-desktop doesn't seem to have an option for it).

I might just have to fork tinder-desktop.

@mayeaux
Copy link
Member

mayeaux commented Nov 28, 2016

Tinder made an update, you guys may have to fork this and fix it. You can check tinder-desktop for the latest version of how to get a token.

@AndrewPrifer
Copy link

Hey guys, here's a short and sweet (~30 lines) working implementation in Python: https://git.io/vMNgR. I guess you should be able to translate the Robobrowser commands into Zombie.

@AndrewPrifer
Copy link

TLDR; The issue is probably with Zombie.
So I looked into the code and tried to fix things. The "Server returned status code 404" issue is easily fixed by using the right user agent (Mozilla/5.0 (Linux; U; en-gb; KFTHWI Build/JDQ39) AppleWebKit/535.19 (KHTML, like Gecko) Silk/3.16 Safari/535.19). After fixing the form inputs (the fields should be looked up based on name and not id, those will vary), I found a strange issue that could be a bug in Zombie. If you leave runScripts on, the whole response body is overwritten with gibberish (probably the source code of some script on the page) and the CONFIRM button won't be found. But you need to run JavaScript on the page to get the XHR working after the button is pressed to get the access token. Also, if you turn on JavaScript after the page is loaded so that it doesn't get overwritten but you can still press the button, you get this strange error: "Tinderauth failed: Invalid protocol: fb464891386855067:".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants