Hi, I have my logic working fine in 2.0 api when there is a network re-connection happens. Now converted the code to 3.0 api and while testing, I got an issue that the re-connection doesn't happen to get the tick data and the application stops. In earlier version setMaximumRetryInterval was accepting -1 for infinite retires, but 3.0 doesn't accept negative values. Please let me know what could be the reason for re-connection failure.
Hi, In the new Kite Ticker, you need to provide a maximum number of retries. You need to provide a positive number and we have introduced a new method also to set maximum retry interval.
In the new Kite Ticker, you need to provide a maximum number of retries. You need to provide a positive number and we have introduced a new method also to set maximum retry interval.