Ken Yee
Ken Yee
You should be connecting to your own copy of the server. The demo Android client in the app store has no problems connecting to my server...
override sMeteorServer or initInstance in the MyDDPState.java.
You can just import it into Android Studio. There's a build.gradle.
Some companies like ours have a policy of not using jitpack :-( There are plugins to make maven central release easier too... In the meantime, we build and put it...
FYI, we found a workaround...set the connectionPool in the builder so it uses a new connection pool w/ a size of zero and also turn off HTTP/2 support by setting...
yep...3.6.0 unfortunately. Thought about rolling back to pre-http/2 support but that would mean 2.2 which is too far back because of all the okhttp3 dependencies :-(
N-1 requests being lost is fine if the connection is down. The issue is that it doesn't recover when you bring the network back up...i.e., the broken idle connection objects...
@swankjesse : I couldn't figure out how to write a test for this because making all the sockets disconnected was happening at at an OS level. Tried to write and...
Essentially...not that they're failing silently, but they're dead sockets and they're stuck in the pool. We traced through a bit of the code and saw some code that was pulling...
I'm sure it's not. We don't see any SSL Handshake exceptions. This bug is actually probably two bugs because we had to disable the connection pool *and* the HTTP/2 support....