Closed lastmeta closed 2 years ago
/// this isn't getting executed when the peer closes the client:
unawaited(client.peer.done.then((value) async {
streams.client.connected.add(ConnectionStatus.disconnected);
print('streams.app.active.value ${streams.app.active.value}');
if (streams.app.active.value) {
streams.client.client.add(null);
}
I think the services.client.scope fixes this as long as we use it.
Describe The Bug
sometimes if the app has been open for a while, like more than 5 minutes and you got to perform an action on the client it'll error, saying the client has no connection anymore.
Log Output
Additional Context
we need to make sure we know when we're disconnected from the server - I think the server disconnects us then we don't get the message or something, so we don't reconnect.
Even though these endpoints don't need an active connection we might as well push everything through that connection because we want to maintain it for the subscriptions, I suppose.
Screenshots