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?
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. 2017-01-22 14:53 GMT+01:00 arrase <[email protected]>: > Printing the trace was enough, I already have the base of the project > working, I had too many hours programming and forget something so simple > > > http://onpanic.org > > El 21 ene. 2017 22:33, "Mark Murphy" <[email protected]> escribió: > > On Sat, Jan 21, 2017, at 16:14, arrase wrote: > > Ouch! > > Sorry, I did not mean to be harsh. There is little I can tell you > without that stack trace, though. I do not log those exceptions > automatically, for privacy reasons -- policies for logging are up to the > app developer. > > > I was not printing the trace .... maybe I should take a break .... but > > I'm so close ... thanks :) > > If the stack trace does not make sense, or you cannot determine how to > fix it, write back here with the details, and I can try to help. > > -- > 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: [email protected] > > >
_______________________________________________ List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To unsubscribe, email: [email protected]
