Skip to content
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

Missed Messages Possibility #1293

Open
preechaw opened this issue Mar 14, 2025 · 0 comments
Open

Missed Messages Possibility #1293

preechaw opened this issue Mar 14, 2025 · 0 comments
Labels
🪲 bug Something isn't working

Comments

@preechaw
Copy link

preechaw commented Mar 14, 2025

The ntfy.sh Android app may lose the stream connection. When the app is reopened, the stream connection will be established, which is great. However, if the user doesn't pull down to refresh, they might miss some messages.
Let's say the last message id before the connection was lost was 1234. While there is no connection, there are two messages IDs 1235 and 1236. The user launches the app and the connection is reestablished. A new message ID 1237 is delivered. Now the "since" value has become 1237. Those two messages 1235 and 1236 will become inaccessible.
This can be reproduced by force stopping the app.

One possible solution is to let the app send poll=1&since=1234 at the time of connection reestablishment. Then 1235 and 1236 won't be missed.

Another possible solution is to set poll=0&since=1234 for the reconnection without another call with poll=1. This should be enough to prevent missed messages.

@preechaw preechaw added the 🪲 bug Something isn't working label Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🪲 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant