Open vertigo220 opened 2 months ago
Please change the title to "Don't block numbers from contacts while using wildcard". It will be easier to find and more understandable without reading the details.
Done
I understand the need for patience and realize you guys have a lot on your plate, but is there much hope of this being fixed soon? Unfortunately, this is an absolute show-stopper for me, and I can't use this app as it is, since I can't see certain conversations, and I can't unblock these number ranges, otherwise I'll get flooded with spam calls again.
@vertigo220 I'll check it out around next week.
Or sooner because this also affects the Phone app, which will be updated soon.
Checklist
Feature description
This is a two-fold issue regarding an oversight in number blocking which results in blocking calls/texts erroneously. The main problem is that it blocks numbers even if they're in contacts if they fall within a wildcard range. I don't see why this would ever be desired behavior, and so it seems it should never block such numbers, but at the very least there should be an option for this. The second problem is that blocked numbers set in one app (phone or messages) are carried over into the second. While this is good and probably preferred most of the time, it wasn't obvious. The combination of these two issues resulted in messages from family and friends not showing up because I had blocked their/my area code in the phone app in order to block neighborhood spoofing calls (e.g. blocking +1555* resulted in a contact with number 555-123-4567 being blocked). It should be clearer that these block lists are shared between the apps, but the main issue is that calls/texts from numbers in contacts should never be blocked by wildcards, and only if those numbers are specifically blocked.
Why do you want this feature?
I want to be able to block using wildcards without inadvertently blocking friends/family/etc. Wildcard use is necessary for the block feature to be of any real use, yet the current design makes their use highly problematic.
Additional information
No response