-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App can take minutes to notify endpoints about new incoming parcels (Internet sync) #275
Comments
I haven't noticed this recently so I'm taking this out of the public alpha launch project. |
I'm noticing this occasionally on Android 8 (Nexus 5X): Awala logs:
Relevant logs in Letro when it works (notice the 3-minute delay):
|
I tested with the Ping app, and the worse case I've seen is 8 seconds of delay, if I previously killed the Ping app. I did notice that the current version of Ping is using the old version of the SDK, that still has this issue: relaycorp/awala-endpoint-android#341 This means that sometimes the Ping app was notified, but it crashed silently in the background, and did not receive the message. Maybe those minute delays you saw were from multiple notification attempts (other parcels were received) until one worked? Otherwise, more reproduction steps for this issue would be very helpful. |
I can't remember 🤔
Indeed... Unfortunately (or fortunately?), this is extremely rate in both Awala Ping and Letro. Is there any logging that we should consider adding, so we have more info next time it happens? |
If the issue is a background crash, it may be hard to get the logs for that, because logcat may have already restarted the session. What would help is a longer log from the Awala app. Did it get more parcels and retry Notifying in those 3 minutes? |
Can't remember 🤔 |
I'm using the echo app with access to the Internet, and I can see in the Android Gateway logs that my parcel is being sent and received very quickly. However, the echo app isn't notified about the new parcel until a few minutes later. I can reproduce this easily, though not 100% of the time.
Here's an example:
As you can see, the parcel
9cb43ec0-ef23-48fc-96bb-195e812d4761
was collected 1.16 seconds after its delivery started. However, I could see the notification on the echo app around 2 minutes later, but neither the echo or gateway apps currently offer any logging to confirm this (I'll be adding some in a PR).The text was updated successfully, but these errors were encountered: