ERROR: Timeout exceeded while waiting for event when using tinder-access-token-generator v

[brunetton]

Hi,

I'm using to use tinder-client/ for a while getting a facebook token from my own and using createClientFromFacebookAccessToken().

But today I wanted to try auto login with puppeteer. But I get a ERROR: Timeout exceeded while waiting for event with this snippet:

import { createClientFromFacebookLogin } from "tinder-client"

async function main(args) {
  const client = await createClientFromFacebookLogin({
    emailAddress: "myEmailAddress",
    password: "myPassword"
  })
  console.log("Got client !")
}

main()

After a while I found that this is due to version 2 of tinder-access-token-generator: npm list gives:

└─┬ tinder-client@4.1.1
  ├─┬ axios@0.18.1
  │ ├── follow-redirects@1.5.10 deduped
  │ └── is-buffer@2.0.3
  └─┬ tinder-access-token-generator@2.0.0

Using dev version of tinder-client (that uses tinder-access-token-generator v3), everything is OK :) (for people that are interested, this is done cloning tinder-client repo and using npm link command).

So here is the request: can you please publish a release of tinder-client that uses tinder-access-token-generator v3 ?

Thanks !

[jaebradley]

@brunetton what version of tinder-client are you using?

As of v4.1.2, tinder-client should have a dependency to tinder-access-token-generator (see #113 or checkout the package.json on master).

Does installing v4.1.2 resolve these errors?

[ndmgrphc]

This is still an issue but it's likely going to be until there's a way to deal with facebook issues. If fb is blocking the oauth for any reason (blocking the login, etc) it's going to choke because there's no error handling on the puppeteer client. Would be cool to expose a way to let us pass our own facebook oauth token generator so we could manage that logic using our own special fb sauce.

[jaebradley]

@ndmgrphc I think it would definitely be possible to allow the API user to pass a token generator.

I was curious if you knew what is causing the issues above? If so, I can fix tinder-access-token-generator.

[ndmgrphc]

Being sent through the recaptcha + mobile confirmation number flow is what's causing it. Even using puppeteer-extra-plugin-stealth to hide chromium isn't enough. So really you need a lot of tools here including clean residential proxies.

• I understand the role of tinder-access-token-generator now, I didn't before, sorry. I would almost suggest making that pluggable but it's easy enough to make your own. At this point we cannot even seem to get a token.