Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
sharing screen of android contacts with e164 numbers is showing the wrong number
See original GitHub issueSteps to reproduce:
- have a contact with a phone number in the e164 format
- share the contact with the barcode scanner
As you can see, the barcode scanner is displaying the country prefix (+49 since it is a german phone number), but it somehow cut off the + character.
The data encoded in the qrcode is correct, though.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Fix Mixed Up Numbers in the Android Contacts - TechRounder
1. Why are My Contacts Showing up as Numbers? ... It might be due to some sync error. First, make sure that you...
Read more >"Failed to format contact number to E.164. Please set Country ...
An article about the error: "Failed to format contact number to E.164. Please set Country on Contact"
Read more >Contacts is incorrectly adding a number to a contact, thereby ...
Contacts is incorrectly adding a number to a contact, thereby causing problems · 1. Go to contacts.google.com · 2. Delete both contacts, Erica...
Read more >Android know international number's country code
Basically I will have a list of numbers in database in E.164 format. But usually numbers in contacts are not in the same...
Read more >SIP Trunk rules/stripping saves wrong number in the ... - 3CX
But the number is not stored in the Call History in its original +33 XXXX format but rather as 0XXXXX. It seems the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was planning to release a ‘10th anniversary’ release in a couple months
allowing
+sounds reasonable, since it matches the content of the qrcode and is a valid part of a phone number.Thanks for fixing this! Can you estimate when this change will arrive in the playstore version?