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

Notifications when logged out / offline #5763

Open
thoughtsunificator opened this issue Sep 18, 2023 · 1 comment
Open

Notifications when logged out / offline #5763

thoughtsunificator opened this issue Sep 18, 2023 · 1 comment

Comments

@thoughtsunificator
Copy link

On iOS 16.6.1, Zulip v27.209, I receive notifications from Zulip when I am offline and also when I am logged out.

@gnprice
Copy link
Member

gnprice commented Mar 4, 2024

Thanks for the report! Sorry for the delayed reply.

I'm not sure what you mean by "offline"; can you elaborate? If it's just that the app isn't already running, then getting notifications in that case is normal — it's the major thing that notifications are for.

Notifications when logged out sounds like a surviving version of the previous issue #3469. I think it's probably the case that if you log out at a time when your device can't reach the server, the server will never learn it should stop sending you notifications and you'll keep getting them. I agree that isn't great behavior.

For the moment, two workarounds are:

  • You can remove the Zulip app from your device completely, and then reinstall it. That should eliminate any notifications that you were getting from previous logins.
  • If you're still using the account in question, just not on that device, then you can log into it again and out of it again, at a time when your device has a good network connection. That will resend the request to the server to stop sending notifications.

We should also fix the behavior so it works correctly in the first place. I'm leaving this issue open to track that. (We won't fix it in the current codebase, because we're in the middle of writing a new app to replace it; but the new app will have the same issue until we take care of it, so we'll just transfer this issue over to there.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants