How to handle `RTK_SERVER_NOT_REACHABLE`
CompletedWhen I call `INetworkRTKManager#startNetworkRTKService`, sometimes - and I'm not clear why - the completion callback is called with the error `RTK_SERVER_NOT_REACHABLE`. I do not see any particular reason why `startNetworkRTKService` succeeds in some cases and fails in others. However, once I receive this error it doesn't appear to matter what is done next - nothing short of relaunching the application allows a successful `startNetworkRTKService` call to be made. Often the error occurs after a single successful pair of calls to `startNetworkRTKService` / `stopNetworkRTKService`, but sometimes it is possible to connect and disconnect several times before the error occurs.
Do you have any guidance on how to handle the RTK_SERVER_NOT_REACHABLE error?
-
Given that I can reliably (I would say at least 90% of the time) successfully start the RTK service by closing and restarting the app, I do not feel that the instability of the hotspot is an adequate explanation for why the SDK, at some point, always returns `RTK_SERVER_NOT_REACHABLE` when stopping and restarting the RTK service.
Please sign in to leave a comment.
Comments
3 comments