You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using phonenumberslite 8.13.16, and noticed that when I parse a US code in the format 1(1XX)YYY-YYYY, the national number is parsed incorrectly as XXYYYYYYY instead of 1XXYYYYYYY. This does seem to be present in the Java version as well, see 1(123)4567890 , which is parsed incorrectly, vs 1(223)4567890, which is parsed incorrectly.
That is true, but the code does not raise an Exception, just returns an incorrectly parsed number, so it is still an issue as the downstream code has no way of knowing the number was incorrect. Furthermore, if you do enter +11234567890, it does not complain that it is an invalid number.
I am using phonenumberslite 8.13.16, and noticed that when I parse a US code in the format 1(1XX)YYY-YYYY, the national number is parsed incorrectly as XXYYYYYYY instead of 1XXYYYYYYY. This does seem to be present in the Java version as well, see 1(123)4567890 , which is parsed incorrectly, vs 1(223)4567890, which is parsed incorrectly.
Putting a
+
sign in front does resolve the issue:I have noticed the issue using python 3.9 and 3.10.
The text was updated successfully, but these errors were encountered: