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
{{ message }}
This repository has been archived by the owner on Sep 1, 2021. It is now read-only.
When the app shuts down, the service is being killed and restarted, see 55348e7. However it takes some time between the service down and back up (approx 10-30 seconds on Honor 5C) and during this time we may miss some notifications.
This is also happening because of the way we're deciding upon if a roll is new or not. Rolls are kept in service RAM memory and a diff is created between two pulls. When the service restarts the state is lost.
We could save that state on disk, however if the app doesn't run for a while, but the player still rolled with this address (not in the app), next time he opens, it will show lot of notifications.
We could also still save on disk, but ignore rolls that are older than a given time period so we don't notify on them.
The text was updated successfully, but these errors were encountered:
When the app shuts down, the service is being killed and restarted, see 55348e7. However it takes some time between the service down and back up (approx 10-30 seconds on Honor 5C) and during this time we may miss some notifications.
This is also happening because of the way we're deciding upon if a roll is new or not. Rolls are kept in service RAM memory and a diff is created between two pulls. When the service restarts the state is lost.
We could save that state on disk, however if the app doesn't run for a while, but the player still rolled with this address (not in the app), next time he opens, it will show lot of notifications.
We could also still save on disk, but ignore rolls that are older than a given time period so we don't notify on them.
The text was updated successfully, but these errors were encountered: