Blacklist matching does not match E.164 numbers
Using version 0.5.17.
I am not quite sure if this is just a visual bug, or if it affects blocking as well.
- I have a number in the call list, 0123456789.
- I tap on it and choose "Add to blacklist"
- I change the number to be +46123456789 (the same number but in E.164 format) and enter a name.
- I go back to the call list and the number is not identified as the same number I have just blocked.
If on step 3 I left it as "0123456789", then on step 4 I see the name instead of the number and I also see "in blacklist". As I mentioned, I do not know if this is just a bug in the UI code or if the blocking functionality will also fail to match against this number.
The reason for why I want to use E.164 format in step 3 is because I'm very often abroad, and when I receive a call from such number abroad it will be identified as "+46123456789" and not "0123456789". To minimize any confusion I store everything in my phone (contacts, etc.) in E.164.
For now my only recourse is to add the same number twice, in the domestic and international formats. However, the app should be using libphonenumber to match the numbers so no matter what format you have in the blacklist, and how the number is identified during/after the call, it will end up always matching.
When that bug is fixed, I also suggest that on step 2 the number is auto-translated to the international (E.164) format as the UI itself suggests you to do.