-
Notifications
You must be signed in to change notification settings - Fork 0
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
mulitple collapsed notifications don't pass attributes to app.js when tapped #22
Comments
Example output of pressing a single notification's entry:
|
Example of pressing a bundled set of notifications:
|
Example of pressing the app's icon in the drawer (nearly identical to the bundled notification save for the extra 'profile: 0' entry)
|
This problem is exacerbated in the testing case where we receive multiple consecutive notifications within a short timeframe. In practice, the user will never receive more than a single notification per release, which occur with a month between them. |
Android occasionally collapses multiple consecutive notifications for the same app into a "bundled" notification. This bundle can be opened by pulling down on its entry in the notification list, revealing each notification.
Tapping a single notification or one of the entries in a bundle after expanding it works as expected, i.e. it passes along the attributes associated with that notification to the app, which allows it to display the correct screen (in our case, the Notify Log screen, since we only have one type of notification currently). In contrast, tapping the bundle of notifications simply launches the app without any of the per-notification metadata (which makes sense, since it would have to arbitrarily choose one notification to pass along, or perhaps an array of them...)
The text was updated successfully, but these errors were encountered: