I can't follow

[Robertos]

The update didn't fix the issue with posting tweet loop.

what I'm trying to do and what's happening:
1. Post tweet tab > posting from a file
-reschedule dot marked
-Random order checked
-random pause 190 - 200
-Max Tweets #1
-repeat min 500
-I'm using media token so tweet format in .txt file is something like #media:C:\Pic.jpg#Tweet txt...

accounts posting fine except the ones hit buy captcha/PV than the endless loop is happening.

log ID 53030
TD version 3.0.2.4 64

[martin@rootjazz]

accounts posting fine except the ones hit buy captcha/PV than the endless loop is happening.

I guess the last update didn't handle that then

Let me check your logs and see if can locate it, as it should most definitely not loop

[martin@rootjazz]

The next update "should" fix this. I shall let you know when it is ready.



Regards,
Martin

[martin@rootjazz]

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

[Robertos]

It's not fixed for me.

[martin@rootjazz]

It's not fixed for me.

I will need logs each time an update was meant to fix it and doesn't to see what is happening

[Robertos]

I'll wait till you fix CSFR/cookie whatever issue it is, coz I think maybe its related.

[Fahad]

I'll wait till you fix CSFR/cookie whatever issue it is, coz I think maybe its related.

Best to not wait.. send the logs so Martin can get better view and detect all this weird related problems.

[Robertos]

I'll wait till you fix CSFR/cookie whatever issue it is, coz I think maybe its related.

Best to not wait.. send the logs so Martin can get better view and detect all this weird related problems.

Currently, there are too many errors I'm receiving in TD. Basic functionality of acc not working like login and write cookies but on the other hand some of the acc working ok. I don't know where to point Martin what is wrong. My logs will make more confusion than help.

[martin@rootjazz]

I'll wait till you fix CSFR/cookie whatever issue it is, coz I think maybe its related.

Without logs, I cannot understand why the assume fix does not work. So I have to wait until someone else apparently gets the same issue and does submit logs. It will happen eventually, but it will delay any fix. If you are ok with that, that is fine. But just to be clear, the more information and logs to analyse the quicker a fix will come.