On Sun, Jan 22, 2017, at 11:21, arrase wrote: > How do you deal with the lag between onEnabled callback of OrbotHelper > and onConnected callback of okhttp3 and the real available state of > 127.0.0.1:8118?
There should be no lag. > I init orbothelper, when onEnabled is called i init > StrongOkHttpClientBuilder then when onConnected is called i run > okHttpClient.newCall(request).execute() but orbot is not yet available > and > i get: > > System.err: java.net.ConnectException: Failed to connect to > /127.0.0.1:8118 > > If i try again it works. If onEnabled() is called, that means that we received a STATUS_ON response from Orbot, which should mean that Orbot is accepting requests. Can you reproduce the problem with the sample apps (e.g., sample-okhttp3) or the test suite (in netcipher-okhttp3)? If so, what version of Android and Orbot are you using? -- Mark Murphy (a Commons Guy) https://commonsware.com | https://github.com/commonsguy https://commonsware.com/blog | https://twitter.com/commonsguy _______________________________________________ List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To unsubscribe, email: guardian-dev-unsubscr...@lists.mayfirst.org
