Write request in initial connect method, breaks on read-only mode about ibkr-api-rust HOT 4 CLOSED

Yes, that is expected if you are using the TestWrapper. It starts sending a lot of test requests upon connecting. You can use TestWrapper as a starting point, and just send the requests you are interested in when connecting (ones that are ok to send in read-only mode). Edit the start_requests method in TestWrapper to change the requests being sent, for your own testing.

And, what you really want to do is just have your own code be responsible for sending any requests, instead of automatically sending requests immediately upon connecting, through your own implementation of the Wrapper trait (you can use TestWrapper as a guide there).

from ibkr-api-rust.

You know, that makes sense, sorry. Didn't mean to make a support question. Appreciate that, I'll close thanks.

from ibkr-api-rust.

By the way, all the data farm messages are ok. TWS Api reports status in addition to actual errors through their error apis

from ibkr-api-rust.

By the way, all the data farm messages are ok. TWS Api reports status in addition to actual errors through their error apis

Yeah, the main error was ["4", "2", "2", "321", "Error validating request.-\'bO\' : cause - The API interface is currently in Read-Only mode."], which came in 50 times or so. I'll proceed with implementing my own Wrapper

from ibkr-api-rust.