-
Notifications
You must be signed in to change notification settings - Fork 987
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
[#11003] Optionally use ENS name as author when building Android notifications #11115
Conversation
Hey @jkrueger, and thank you so much for making your first pull request in status-react! ❤️ Please help us make your experience better by filling out this brief questionnaire https://goo.gl/forms/uWqNcVpVz7OIopXg2 |
Jenkins Builds
|
thanks @jkrueger , is it still wip ? |
I think it's fine, since it's a fairly simple fix. |
98% of end-end tests have passed
Failed tests (2)Click to expand
Passed tests (96)Click to expand |
Hi @jkrueger, did a quick test with the PR build on Samsung Galaxy S10e (Android 10) Send messages from a Fairphone 2 (Android 7)
Send message from both to user C. Notifications for user C are not showing random name or ENS name. Tried if contact status makes a difference.
Another issue, that I think is out of the scope of this PR, is that the notification seems overlaid by the notification for the first message; In this case I send a message from user B first. When sending a message from user A, notification for user C shows the message from user B on top. cc @churik @Serhy |
I’ve tried this in a Genymotion machine, and it did work there. Let me double check |
Another issue is that those ENS names are not going to be verified. So it will display anything that the user sets, but it might not be belonging to the user. |
…roid notifications
@hesterbruikman I've added an extra test that makes sure that the 3-random name gets displayed if the ens name is present in the message, but empty. I think that may fix your case. @cammellos Just so I understand this right, before I dig into the status-go code. The notification gets created from data that came from another user's message. What you want is, that whatever ENS name comes in the message gets verified on the receiver's side? |
@cammellos I've taken the time to read the go code, so I understand the flow of information better, and where the ENS name comes from, and gets verified. I have a couple of proposals for how to pass this information through to the android notification handler. I wrote some code that could be discussed, that solves the problem, but I feel this reaches fairly deeply into the application logic, in ways that could break things easily. Teo mentioned that you're off work at the moment. It would be good if we could quickly chat next week, and see how we sync this fix with any potential status-go work. I will write a regression test for this bug in status-rect in the mean time, and add it here. |
@jkrueger Thanks for the contribution, |
@andremedeiros That's fair enough. I'll wait for you, or Teo to get in touch with me. |
fixes #11003
Summary
This was an issue where the ENS name was not extracted from a chat message properly. The PR optionally gets the ENS name when present, and uses the 3-random name otherwise.
Review notes
Testing notes
Platforms
Areas that maybe impacted
Functional
Steps to test
status: wip