You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Sorry about the vague title, but I don't really know how to summarise it, or even if it's one or more issues.)
I was using Letro this afternoon until 18:00 via WiFi, and everything worked fine. Then I left that place and switched to 5G.
At 20:56, connected to another WiFi network, I open Letro and send a message, but nothing happens. So I open Awala and see the usual "You're disconnected from Awala" screen, so I checked logcat and here's what I found:
Letro: The message was indeed sent to Awala. Interestingly, there are no logs saying that we're setting up the Awala SDK, so I'm guessing Awala.setup() wasn't called again at 20:56, but I can see the log entry from a few hours ago. Unfortunately, as I was writing this logcat lost the logs prior to 20:56, but here's letro-logs.txt.
I triggered a network change event by switching from WiFi to 5G, and then the app reported that it was connected to the Internet. When I checked the awala-logs.txt, I found that it'd just delivered the parcel from Letro.
So, two questions:
Why didn't that OutgoingMessage.send() call from the SDK didn't cause the app to send the parcel to the Internet gateway?
Why wasn't this app running the public sync with keepAlive=true whilst I was using Letro?
I wonder if the problem is that the last time we called GatewayClient.bind() was a few hours ago. If so, is there anything we can do in the SDK automatically?
The text was updated successfully, but these errors were encountered:
It does look like the main issue is that Awala stopped running the PublicSync. The most likely reasons for that are:
It couldn't reach the public gateway, and it didn't recover from that state by itself
No app is bound to the Awala app
I think it's more likely the issue is 1) because you saw You're disconnected from Awala, which is unrelated to the Public Sync running, only to the connection state. So I'll investigate why the Awala app is losing connection and not recovering by itself from it.
Fixes#717
We're repeating the connection state check every 5 seconds. But the 3 checks themselves did not have timeouts, so that meant it could take several minutes just to complete one check. I've now capped each check to 5 seconds as well, so worse case scenario it could take 20 seconds between connection state checks.
(Sorry about the vague title, but I don't really know how to summarise it, or even if it's one or more issues.)
I was using Letro this afternoon until 18:00 via WiFi, and everything worked fine. Then I left that place and switched to 5G.
At 20:56, connected to another WiFi network, I open Letro and send a message, but nothing happens. So I open Awala and see the usual "You're disconnected from Awala" screen, so I checked logcat and here's what I found:
Awala.setup()
wasn't called again at 20:56, but I can see the log entry from a few hours ago. Unfortunately, as I was writing this logcat lost the logs prior to 20:56, but here's letro-logs.txt.keepAlive=false
-- unfortunately, logcat lost these logs as I was writing this.I triggered a network change event by switching from WiFi to 5G, and then the app reported that it was connected to the Internet. When I checked the awala-logs.txt, I found that it'd just delivered the parcel from Letro.
So, two questions:
OutgoingMessage.send()
call from the SDK didn't cause the app to send the parcel to the Internet gateway?keepAlive=true
whilst I was using Letro?I wonder if the problem is that the last time we called
GatewayClient.bind()
was a few hours ago. If so, is there anything we can do in the SDK automatically?The text was updated successfully, but these errors were encountered: