Jonathan Rainville 2445cda3e0
fix(contacts): fix blocking a non-contact sends a signal to the other (#4799)
Fixes https://github.com/status-im/status-desktop/issues/13545

The code is correct in sending an updated CR to make sure the sync doesn't sync back the previous state or at least overrides it.
However, if we never were a contact with the person sending us a CR, and we block them, it sends them a "you got removed" message, which first doesn't make sense but also could let them know they got blocked/ignored.
The trick is just to make sure we added them first. Then dismissing the CR makes sense.
2024-02-26 12:49:04 -05:00
2021-06-16 16:19:45 -04:00
2023-06-23 12:01:30 +01:00
2023-01-13 17:52:03 +00:00
2024-02-23 11:26:31 +01:00
2024-01-22 13:08:58 +01:00
2023-11-18 02:26:34 +02:00
2022-03-28 13:14:12 +01:00
2022-03-28 13:14:12 +01:00
2021-07-20 10:57:38 +02:00
2023-11-09 14:35:59 +08:00
2023-01-13 17:52:03 +00:00
2024-02-23 11:26:31 +01:00
2022-12-29 14:16:19 +08:00
2024-02-23 11:26:31 +01:00
2022-07-17 15:37:14 +02:00
2023-12-05 12:29:27 +08:00
2023-11-13 14:06:32 -05:00
2023-10-05 14:11:38 +01:00
2023-10-12 15:21:49 -04:00
2016-09-21 10:00:29 +08:00
2024-01-22 13:39:38 +01:00
Description
The Status module that consumes go-ethereum
https://status.im
Readme
Languages
Go 98.6%
Python 0.8%
Shell 0.3%
Makefile 0.1%
Groovy 0.1%