-
Notifications
You must be signed in to change notification settings - Fork 235
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: Support tapping a notification to open the conversation #123
Comments
It might be useful to study how we do this in zulip-mobile. With , we simplify the case that was the most opaque in |
gnprice
added a commit
that referenced
this issue
Jun 14, 2023
gnprice
added a commit
that referenced
this issue
Oct 31, 2023
This implements most of the remaining work of #320. It doesn't yet deliver most of the user-facing value: for that, the remaining piece will be to make notifications appear when the app is in the background as well as when it's in the foreground. I have a draft for that and it works, but the tests require some more fiddling which I may not get to today, so I wanted to get the bulk of this posted for review. Many other improvements still to be made are tracked as their own issues: most notably iOS support #321, and opening a conversation by tapping the notification #123.
gnprice
added a commit
to gnprice/zulip-flutter
that referenced
this issue
Nov 2, 2023
Still only on Android; iOS support for notifications in general is coming next. Fixes: zulip#123
chrisbobbe
pushed a commit
to gnprice/zulip-flutter
that referenced
this issue
Nov 6, 2023
Still only on Android; iOS support for notifications in general is coming next. This also only applies when the app is already running (either in the foreground or the background) when the notification is opened. The case where the app isn't already running and is launched from the notification will be handled in an upcoming commit. Fixes-partly: zulip#123
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After #122.
The text was updated successfully, but these errors were encountered: