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

Sometimes PN does not redirect user into correct chat if some other chat was opened at the moment of redirection (Android) #17790

Closed
pavloburykh opened this issue Nov 1, 2023 · 1 comment · Fixed by #17853
Assignees
Labels

Comments

@pavloburykh
Copy link
Contributor

Followup of #17721 cc @yqrashawn

Reproducing on Android 12, Samsing Galaxy A52. Bug is not reproducible every time

Preconditions: User A (Android) turns on push notifications

Steps:

  1. User A opens 1-1 chat with User B
  2. User A closes the app
  3. User B sends mention/reply to User A in community channel
  4. User A taps on PN
  5. See if User A is redirected into community cahnnel

Actual result: sometimes User A remains on 1-1 chat screen and is redirected to the channel. At the same time, the message in channel appears as read despite User A in fact has not opened the channel.

redirected_wrong_chat.mp4

Status-debug-logs (76).zip

Expected result: User A should be redirected to the right chat upon PN.

Additional Information

  • Status version: nightly
  • Operating System: Android
@Parveshdhull
Copy link
Member

Parveshdhull commented Nov 6, 2023

Hi @yqrashawn,
when we are navigating to 1-1 chat, we always pop-to-root. But we don't do this in case of community chat (because we need to keep the community screen open). (reference)

Still, we have (close-chat false) in the navigate-to-chat event that should have closed the current 1-1 chat (even if the view is not destroyed).
I didn't look much into the issue and am not sure why current-chat-id didn't update while navigating, still, the issue might be related to this. We probably need to pop-to-root before navigating to community chat from notification.

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

Successfully merging a pull request may close this issue.

4 participants