Hi Linvi,
I don't think there is any problem other than the value in the Exception being wrong.
I have always had occasional timeouts when the application is first launched (hundreds of requests get sent in parallel, and I assume Twitter has some anti-spam/flood mechanism that drops some of the connections) and so I believe the timeouts to be genuine.
Once the application is running, the timeouts stop and everything runs smoothly (apart from the occasional timeout), as has been the case when using previous versions of Tweetinvi. The only thing that threw me after the update was the timeout value being wrong in the exception.
Unless I've misunderstood what you mean?
Cheers,
Josh
I don't think there is any problem other than the value in the Exception being wrong.
I have always had occasional timeouts when the application is first launched (hundreds of requests get sent in parallel, and I assume Twitter has some anti-spam/flood mechanism that drops some of the connections) and so I believe the timeouts to be genuine.
Once the application is running, the timeouts stop and everything runs smoothly (apart from the occasional timeout), as has been the case when using previous versions of Tweetinvi. The only thing that threw me after the update was the timeout value being wrong in the exception.
Unless I've misunderstood what you mean?
Cheers,
Josh