Couldn't get ct0 cookies to set x-csrf

[Aturingtest]

FAILED: 23284762398476238742 : Couldn't get ct0 cookies to set x-csrf
My other accounts work fine just this one.
Done several forced logins all of them worked fine.
Newest version of TD
Was working fine yesterday

[Aturingtest]

Solved I did a reinstall from fresh and it worked fine I had been using that instance for a while so needed to be refreshed I suppose

[martin@rootjazz]

It's a known issue at the moment.

What it looks like is, twitter are now detecting a missing ID on the search requests. They allow a few request, then cancel the cooking forcing a login, in which they give you a challenge.

IF so, the solution is browser for 100% of the app. I Am working on search browser updates to allow this and work better. I hope to have those this weekend


the latest update has lots of new updates to try and work better with the ct0 issue, you can assign the custom config:
HELP > CONFIG > ADD OPTION:
ct0_fix


That will store the ct0 for the session and just reassign it if twitter tries to cancel it. WARNING IT;S A TESTING FEATURE

[hooahjuice]

Should be issue number 1 you are working on.

[martin@rootjazz]

Should be issue number 1 you are working on.

Dont' spam reply to every post. I have (X) time, every minute I open a forum post to see the same reply from you takes away that time I should be working on the update. I know the update is needed, having to read the same reply from you in multiple threads just delays the function getting completed.