-
Notifications
You must be signed in to change notification settings - Fork 79
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
Rejecting a Contact Request blocks further attempts to add user as a contact #16817
Comments
I think this was designed as a "feature" to protect from spam; CC @jrainville @iurimatias do we still want that? 🤔 |
Thanks @caybro for taking a look! What if the user rejects the contact by mistake? It would be nice to give the user one more chance. |
Yeah, it might be by design. We don't want spammers to know that they got declined so that they can try again.
I think User 2 can then be the one sending the contact request and User 1's request should then show as "completed" and they would be mutual. Maybe there is an issue there though. I can try to reproduce and fix if that's the case. |
Thinking about this usecase again; I think it's even easier to the person receiving the CR to just go ahead and straight "ban" the other user. That way, the request at least shows up in the Banned section, and can be revisited at any later time |
Do you mean the "reject" should act as a block? Do note that block straight up makes it so that User 2 would not be able to see any message from User 1 in that case (in a community for example). If you just mean that rejecting should put them in another tab, I think it makes more sense. We had commented out code for that I think (because it never worked and it was super messy). We have a similar thing in the community for rejected requests. |
Yeah, I meant for the "Reject CR" to work something like that 👍 |
@virginiabalducci I just tested this and it works as expected from my POV of the requirements. Here's what I did:
Now, User 2 doesn't have a CR anymore and the state for User 1 stays as it was, because we do not want to let others know we rejected them Now I want to "undo" that. Here's how:
Nothing else is needed here. They are now mutual contacts, because they are both in a state where they send a contact request to each other (mutual). Two improvements are possible though:
I will try to fix the second point now. I don't know if we should create a new issue for the bug or for the new feature? What do you guys think? |
Just as confirmation, we have a test case in status-go that does just as I said here: // The scenario tested is as follow:
// 1) Alice sends a contact request to Bob
// 2) Bob declines the contact request from Alice
// 3) Bob sends a contact request to Alice
// 4) Alice and Bob are mutual contacts (because Alice's CR is "pending" on her side), Both CRs are accepted
func (s *MessengerContactRequestSuite) TestBobSendsContactRequestAfterDecliningOneFromAlice() { |
… or updating the AC notif Fixes status-im/status-desktop#16817 There were two issues. When dismissing a CR, then sending one back, it did mark the two contacts as mutual and showed the 1-1 chat. However, the message sent in the second/final CR was not shown in the first person's client. Also, the AC notification for the first user didn't update, so it got stuck in a "pending" state. Those two issues are fixed now with a test to confirm.
I opened a new issue for the new tab: #16844 |
… or updating the AC notif Fixes status-im/status-desktop#16817 There were two issues. When dismissing a CR, then sending one back, it did mark the two contacts as mutual and showed the 1-1 chat. However, the message sent in the second/final CR was not shown in the first person's client. Also, the AC notification for the first user didn't update, so it got stuck in a "pending" state. Those two issues are fixed now with a test to confirm.
…e or updating the AC notif Fixes status-im/status-desktop#16817 There were two issues. When dismissing a CR, then sending one back, it did mark the two contacts as mutual and showed the 1-1 chat. However, the message sent in the second/final CR was not shown in the first person's client. Also, the AC notification for the first user didn't update, so it got stuck in a "pending" state. Those two issues are fixed now with a test to confirm.
Fixes status-im/status-desktop#16817 There were two issues. When dismissing a CR, then sending one back, it did mark the two contacts as mutual and showed the 1-1 chat. However, the message sent in the second/final CR was not shown in the first person's client. Also, the AC notification for the first user didn't update, so it got stuck in a "pending" state. Those two issues are fixed now with a test to confirm.
Bug Report
Description
user 1 sends a contact request to user 2. User 2 rejects. The contact request gets stuck and these users cannot add each other.
There seems to be an issue triggered when the user rejects the contact request, blocking any other ways to add the contact.
Steps to reproduce
Expected behavior
As user 1, when going to Settings > Messaging > contacts > Pending Requests, the request sent to user 2 should be deleted
Actual behavior
As user 1, when going to Settings > Messaging > contacts > Pending Requests, the request sent to user 2 is still showing up. I've tested with 3 new users, and the behavior can be reproduced.
Also, if the user 2 sends a contact request to user 1:
If user 1 blocks and unblocks user 2 to remove them from the 'Pending Requests', when trying to add them as a contact, user 2 cannot add user 1.
Additional Information
test 054 logs.zip
test054 geth.log.zip
test053 geth.log.zip
test 053 logs.zip
The text was updated successfully, but these errors were encountered: