-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Swiping a notification to dismiss should not dismiss all notifications #8268
Comments
Tried app version 11.4 on a Pixel 2 XL running Android 9 and couldn't reproduce it when dismissing one of two notifications. I tried with one comment and one "Like" notification and been able to dismiss the "Like" only. Are there perhaps more specific steps to reproduce? Thanks! |
@hypest I'll keep an eye out for how to reproduce. Perhaps, the issue only surfaces if there are multiple of the same type (e.g. all comments) |
Moving to the |
Thanks, @designsimply! I think I've noticed this happening more frequently when there are "non-standard" notification types in the list. For example X-post notifications. Perhaps that's related. |
I've looked into this issue, but it's difficult to fix since we are not able to reproduce it. I've tested different scenarios and everything worked as expected for me. I have two guesses what might be causing the issue
@jblz I'd be great if you could post the application log when this issue happens again. (Click on "Me" -> "Help & Support" -> "Application log". Thank you 🙇 Note: I'll keep testing this issue on the production version of the app. Hopefully, I'll encounter it sooner or later. |
I'm closing the issue since I wasn't able to reproduce in the latest version of the app Screen_recording_20240304_181916.mp4 |
Expected behavior
Only the item swiped to be dismissed
Actual behavior
The item disappears & then all app notifications disappear
Steps to reproduce the behavior
Have more than one notification items, swipe one away
Tested on [device], Android [version]
Pixel, Android versions 8 & 9
The text was updated successfully, but these errors were encountered: