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

Duplicated activities on new messages with the Zulip Android app (both legacy and beta) #1353

Open
1 of 6 tasks
pjb7687 opened this issue Feb 10, 2025 · 3 comments
Open
1 of 6 tasks

Comments

@pjb7687
Copy link

pjb7687 commented Feb 10, 2025

Android Zulip app (both legacy and beta) creates new activities when it is reactivated by touching push message for a new message, even if the activity for the chat is already open.

To reproduce:

  • On the Android app, receive a DM.
  • While the chat activity is open, press home button to make the Zulip app goes background.
  • Receive another DM from the same person.
  • Touch the push message toast to reactivate Zulip app.
  • Press back button to remove the duplicated activities.

Zulip Server and web app version:

  • Zulip Cloud (*.zulipchat.com)
  • Zulip Server 9.x
  • Zulip Server 8.x
  • Zulip Server 7.x
  • Zulip Server 6.x or older
  • Other or not sure
@timabbott
Copy link
Member

Are you sure the problem isn't that you're getting notifications for both apps? The apps are independent, so it's expected that if you have both enabled for notifications, you'll see two notifications for every message, one for each app.

@pjb7687
Copy link
Author

pjb7687 commented Feb 10, 2025

Are you sure the problem isn't that you're getting notifications for both apps? The apps are independent, so it's expected that if you have both enabled for notifications, you'll see two notifications for every message, one for each app.

Yes I am pretty sure this is not that - At the moment I am only using the beta app.

The problem was there with the legacy app but I did not report the bug as it will be eventually replaced with the new flutter based one, but the same problem persists even after the framework change.

@pjb7687

This comment has been minimized.

@alya alya transferred this issue from zulip/zulip Feb 13, 2025
@PIG208 PIG208 added this to the M6: Post-launch milestone Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants