-
Notifications
You must be signed in to change notification settings - Fork 65
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
MM-53924 - Mobile push notifications #503
Conversation
|
||
func buildPushNotificationMessage(senderName string) string { | ||
// TODO: translations https://mattermost.atlassian.net/browse/MM-54256 | ||
return fmt.Sprintf("\u200b%s is inviting you to a call", senderName) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was kind of funny. For a long time I thought the push notification was being rewritten somewhere because what should have been Sender Name is inviting you to a call
was turning into Sender Name: is inviting you to a call
in condensed, and
Sender Name
is inviting you to a call
in expanded view.
It turns out that (at least my) Android device does its own processing, and if it notices the prefix of the notification is the same as the sender name, it elides it. Thanks, Android. Super helpful.
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #503 +/- ##
========================================
- Coverage 5.50% 5.43% -0.08%
========================================
Files 23 24 +1
Lines 4265 4379 +114
========================================
+ Hits 235 238 +3
- Misses 4012 4124 +112
+ Partials 18 17 -1
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Gave this a first quick pass and left some minor comments.
# Conflicts: # go.mod # go.sum # server/plugin.go # server/utils.go
@cpoile for the Android expanded notification state, do we have any control over the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👍
# Conflicts: # go.mod # go.sum
@matthewbirtch Making a custom button will take some native work, so I think we've got to prioritize it as new effort. Sound good? |
no problem, can we just hide the |
@matthewbirtch Edit: I'm looking into it, maybe it is in our native code... |
@matthewbirtch Ok, I think I figured out Android at least. It's our own native code that gives the Okay button. Will be fixed once mattermost/mattermost-push-proxy#106 and mattermost/mattermost-mobile#7534 roll out. |
Okay, thanks for investigating @cpoile. I think I'm good to approve this then |
Summary
DM Channels:
GM Channels:
Regular Channels (only if the user receives the notification naturally):
You can see that Android does it's own processing of the message on the user's device, so this might look different based on the user's make & model. (See the inline code comment below for an example of this.)
Ticket Link