Authentication requird

[Emin]

why does it always show this?
https://imgur.com/a/WB5u4gf

[martin@rootjazz]

twitter returned a response that requires the account to authenticate again

[hooahjuice]

Is there a way to address this is on our end?

[Rev]

The biggest problem with this is that, it also terminates all other (or significant amount of) active sessions/cookies on different devices/browsers, which means you will have to sign-in to all the affected accounts one-by-one once again if you are doing this process manually (in case of not using Twitterdub or any other software for your secondary devices/browsers).

From what I have observed, it seems like this is happening because of a recent Twitter update/change and not caused by the Twitterdub software directly (most likely). I believe that Twitter has added some "active-session limit" to their already boggled system to think that they are "getting rid of the automation" on users part. On the software side of things, I believe once Twitterdub creates a number of different active-sessions per account (for multiple of different reasons) and the amount hits the limit that I predicted above is cause of the random "authentication" errors and termination of other active-sessions (on Twitters part).

This is not an easy issue to recreate in a controlled environment but, it happens time to time and is highly annoying/time-consuming to fix (if you got hundreds or more accounts).

[Emin]

overall a complete mess

[zoltan66]

I've encountered this issue in the past while using an older version of TD. The only solution at that time, aside from updating TD to the latest version, was changing the user agent for the affected accounts, and that resolved the problem. In the current version, the issue is automatically resolved when using 'verify login,' so I'm not sure if it's still related to the user agent. However, it's worth mentioning that in the past, this problem seemed to be associated with outdated or old user agents.

[martin@rootjazz]

Is there a way to address this is on our end?

better accounts
better IPs
less spammy so twitter don't want to trigger a login again

[Emin]

Is there a way to address this is on our end?

better accounts
better IPs
less spammy so twitter don't want to trigger a login again

new accounts, registered manually, the first login is normal, then it immediately throws at it

[martin@rootjazz]

Is there a way to address this is on our end?

better accounts
better IPs
less spammy so twitter don't want to trigger a login again

new accounts, registered manually, the first login is normal, then it immediately throws at it

Can you cause the issue?

If so:

Please perform:

1) Clear logs: HELP > LOGS > DELETE

2) Run the action that you are having an issue with.

***
IDEALLY PLEASE DO NOT RUN ANY OTHER ACTIONS AT THE SAME TIME
***


3) If the issue happens again, submit logs:
HELP > LOGS > SUBMIT

then send your logs ID - the first 4 numbers is sufficient (displayed after successful uploading of logs)





Regards,
Martin

[Emin]

better accounts
better IPs
less spammy so twitter don't want to trigger a login again

new accounts, registered manually, the first login is normal, then it immediately throws at it

Can you cause the issue?

If so:

Please perform:

1) Clear logs: HELP > LOGS > DELETE

2) Run the action that you are having an issue with.

***
IDEALLY PLEASE DO NOT RUN ANY OTHER ACTIONS AT THE SAME TIME
***


3) If the issue happens again, submit logs:
HELP > LOGS > SUBMIT

then send your logs ID - the first 4 numbers is sufficient (displayed after successful uploading of logs)





Regards,
Martin

this happens after the program automatically solves the captcha