Zaarrg / DropBot

Drop Bot. Automaticlly Farms every Drop available like Rust for ya and now also your Custom Channel's
396 stars 121 forks source link

cant log in either way #79

Open connormcginty opened 1 year ago

connormcginty commented 1 year ago

When loggings in - using command line it crashes when logging in via browser, twitch won't accept my correct credentials

RedrootDEV commented 1 year ago

same here

KingYam commented 1 year ago

Also having the same problem, Windows 11. Here is output from TTVDropBot-error.txt

2022-10-06 09:32:15: Unhandled Rejection at: Promise {
  <rejected> Error: Navigation failed because browser has disconnected!
      at new LifecycleWatcher (C:\snapshot\TTVDropBot-v2\node_modules\puppeteer-core\lib\cjs\puppeteer\common\LifecycleWatcher.js:95:223)
      at Frame.waitForNavigation (C:\snapshot\TTVDropBot-v2\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Frame.js:261:25)
      at Page.waitForNavigation (C:\snapshot\TTVDropBot-v2\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Page.js:1218:88)
      at C:\snapshot\TTVDropBot-v2\build\Pages\loginPage.js:38:29
      at Generator.next (<anonymous>)
      at fulfilled (C:\snapshot\TTVDropBot-v2\build\Pages\loginPage.js:5:58)
      at processTicksAndRejections (internal/process/task_queues.js:95:5) {
    [stack]: 'Error: Navigation failed because browser has disconnected!\n' +
      '    at new LifecycleWatcher (C:\\snapshot\\TTVDropBot-v2\\node_modules\\puppeteer-core\\lib\\cjs\\puppeteer\\common\\LifecycleWatcher.js:95:223)\n' +
      '    at Frame.waitForNavigation (C:\\snapshot\\TTVDropBot-v2\\node_modules\\puppeteer-core\\lib\\cjs\\puppeteer\\common\\Frame.js:261:25)\n' +
      '    at Page.waitForNavigation (C:\\snapshot\\TTVDropBot-v2\\node_modules\\puppeteer-core\\lib\\cjs\\puppeteer\\common\\Page.js:1218:88)\n' +
      '    at C:\\snapshot\\TTVDropBot-v2\\build\\Pages\\loginPage.js:38:29\n' +
      '    at Generator.next (<anonymous>)\n' +
      '    at fulfilled (C:\\snapshot\\TTVDropBot-v2\\build\\Pages\\loginPage.js:5:58)\n' +
      '    at processTicksAndRejections (internal/process/task_queues.js:95:5)',
    [message]: 'Navigation failed because browser has disconnected!'
  }
}
2022-10-06 09:32:24: Something went wrong...
LukysGaming commented 1 year ago

+1

jennyfercaron commented 1 year ago

I have the same problem

bossman90 commented 1 year ago

+1

FrostFireFury commented 1 year ago

+1

Suitingyak commented 1 year ago

+1

jessielw commented 1 year ago

Same

TomerGamerTV commented 1 year ago

i get something went wrong error

cyberofficial commented 1 year ago

⚠️ take notice of your expiring date as well, just a little bit under the auth code, you'll need to get a new code after that time/date

mrtsntrk commented 1 year ago

@cyberofficial dude your method is successful.

MiranoVerhoef commented 1 year ago

@cyberofficial

I have downloaded your patched version but I’m getting the same errors as the post owner, image

xeryax commented 1 year ago
  • Work Around for Unable to log in on chrome, can also hit F12, under the application tab there should be a 'cookies' section with https://www.twitch.tv in it. that has the auth-code as well
LPRM commented 1 year ago

@cyberofficial

I have downloaded your patched version but I’m getting the same errors as the post owner, image

I have this issue too.

LukysGaming commented 1 year ago

We'll have to wait for the owner to update it i guess

cyberofficial commented 1 year ago

@cyberofficial

I have downloaded your patched version but I’m getting the same errors as the post owner,

@cyberofficial I have downloaded your patched version but I’m getting the same errors as the post owner,

I have this issue too.

If you have my latest build 00.03 Disable channel point collection, (feature i placed in)

Inside settings.json add the line "CollectPoints": false (will add argument for cli soon) Example:

If that doesn't work, i can try a few other methods, but channels points seem to cause many errors right now

LPRM commented 1 year ago

@cyberofficial I have downloaded your patched version but I’m getting the same errors as the post owner,

@cyberofficial I have downloaded your patched version but I’m getting the same errors as the post owner,

I have this issue too.

If you have my latest build 00.03 Disable channel point collection, (feature i placed in)

Inside settings.json add the line "CollectPoints": false (will add argument for cli soon) Example:

If that doesn't work, i can try a few other methods, but channels points seem to cause many errors right now

I have "CollectPoints": false already, scrrenshot below:

Screenshot 2022-10-07 191600

cyberofficial commented 1 year ago

@cyberofficial I have downloaded your patched version but I’m getting the same errors as the post owner,

@cyberofficial I have downloaded your patched version but I’m getting the same errors as the post owner,

I have this issue too.

If you have my latest build 00.03 Disable channel point collection, (feature i placed in) Inside settings.json add the line "CollectPoints": false (will add argument for cli soon) Example: If that doesn't work, i can try a few other methods, but channels points seem to cause many errors right now

I have "CollectPoints": false already, scrrenshot below:

Screenshot 2022-10-07 191600

Your issue means your auth-token is incorrect or expired; you need to generate a new code and update twitch-session.json using the work around method i posted.

LPRM commented 1 year ago

@cyberofficial I have downloaded your patched version but I’m getting the same errors as the post owner,

@cyberofficial I have downloaded your patched version but I’m getting the same errors as the post owner,

I have this issue too.

If you have my latest build 00.03 Disable channel point collection, (feature i placed in) Inside settings.json add the line "CollectPoints": false (will add argument for cli soon) Example: If that doesn't work, i can try a few other methods, but channels points seem to cause many errors right now

I have "CollectPoints": false already, scrrenshot below: Screenshot 2022-10-07 191600

Your issue means your auth-token is incorrect or expired; you need to generate a new code and update twitch-session.json using the work around method i posted.

  • make sure to relog into twitch and click the box that says keep me logged in for 30 days for a longer lasting auth-token

I had just logged in with that token, tried again with new token and now works. Thank you

MiranoVerhoef commented 1 year ago

Did the way you said, with the cookie editor, but the error still comes back unfortunately

MiranoVerhoef commented 1 year ago

@cyberofficial do you have a other cause of the error?

mice verified with disable collect points as well!

TomerGamerTV commented 1 year ago

i tried using the cookie but the app seem to crash than i try to watch any stream

cyberofficial commented 1 year ago

@cyberofficial do you have a other cause of the error?

mice verified with disable collect points as well!

@MiranoVerhoef Can you send the logs?

MiranoVerhoef commented 1 year ago

@cyberofficial let me get them once I’m home!

bossman90 commented 1 year ago

Any news?

omeganot commented 1 year ago

I too had that DropsPage_ClaimDropsReward error. What cleared it for me was removing the Docker container and creating it fresh with my updated auth_token. This might not help you if you're not using Docker, but there could be some caching going on somewhere that needs cleared out.

Edit: Aaaand, I'm running right back into it like y'all are. =/

2relativ commented 1 year ago

Can confirm this issue is still there. Also @cyberofficial since your build does not support command line yet, I had to use another way: I set the claim timer to like 6000000 xD this way it keeps watching and afterwards i just have to remember claiming :D the autoclaim variable didn't work for me :/ btw, running this on Ubuntu with displayless activated. Runs as a systemd task. It retrys 5 times and after that it stops. In my linux cockpit i can simply start the process from my smartphone. Thats good enough for me at the moment :D

Edit: Now running on docker, seems easier for me.

EditEdit: Well, seems like the claim timer is necessary. by this, the command line and docker are effectively broken.