Login Loop - Not Initiating SMS Verifications

[bigjpr83]

Failed JSON response: 403
https://twitter.com/i/api/2/timeline/ho ... ghtedLabel
{"errors":[{"code":326,"message":"To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.","sub_error_code":0,"bounce_location":"https://twitter.com/account/access"}]}
ERROR RESP FROM TWITTER: 326 To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.
* TESTING for known failure text: To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.
WARNING: To protect our users from spam and other malicious activity, this account is temporarily locked: Login required
loop attempt: 1
* FAILED log: Login required loop detected, stopping...
* FAILED log: Login required loop detected, stopping...
Validate account failed

I am getting this message consistently with accounts needing SMS verification. In the past twitterDub has utilized the 5SIM api with no problems and bypassed/verified via SMS but now it is continuously getting stuck here.

Logs submitted: logs_97480

[martin@rootjazz]

I think latest update solves this, although am not 100% I uploaded it.

you can try it:
https://rootjazz.com/twitterdub/updatetesting.html

and I'll do a rebuild later today and let you know



Regards,
Martin

[bigjpr83]

I think latest update solves this, although am not 100% I uploaded it.

you can try it:
https://rootjazz.com/twitterdub/updatetesting.html

and I'll do a rebuild later today and let you know



Regards,
Martin

I can confirm that the latest build/testing release does not solve the problem. Let me know if you need additional logs to help fix.

Thanks!

[martin@rootjazz]

https://rootjazz.com/twitterdub/updatetesting.html

rebuild

If doesn't help, as always submit logs and if I can test the account, export it and send it over. IT could be you are getting a loop flow which was different to what I fixed

Or maybe my fix caused a new issue lol