+624 area-code | US phone number | Shows Invalid Phone for a Valid Phone Number
We recently got an issue related to a phone number where client trying to add new phone number from +624 area code of US and it shows INVALID Phone Number which is false alert.
We are using intl-tel-input for validating phone number for length and serviceable of the phone. This phone area code was introduced in Nov, 2023. Can we get any suggestions or quick fix for this specific area code to unblock client?
Context about Area Code +624: • The area code 624 was assigned in 2023. • It serves the same numbering plan area (NPA) as area code 716, covering Buffalo, Niagara Falls, and surrounding counties in western New York. • The original area code 716 was established in 1947.
Issue: Phone Number +1 624 305 1111 (modified last 4 digits from actual phone number for privacy) - This is not working. In Similar context, if tried with area code 716 +1 716 305 1111 - This works.
Version Details:
- Tried with latest version 25.3.1 but same result
- Actually using 24.x.x version
Similar Issues: #1994 Canadian Phone issue #1961 Ireland Phone issue
Hi there, thanks for raising this.
We use libphonenumber for validation, you can try their demo site here, and this says +16243051111 is not a valid number - link. I understand you're trying to protect your client's privacy, but I'll need a valid number in order to debug this issue.
Also can you tell me: which validation method are you using?
And have you tried with validationNumberTypes set to null?
@jackocnr we are using precise validation. We tried by setting validationNumberTypes to null, says number as invalid
Apologies for the delay in getting back to you. Does the LPN demo page say your number is valid or invalid? If LPN says your number is invalid, you'll need to raise the issue with them. If LPN says it's valid and the latest version of our plugin is still saying it's invalid, then you'll have to give me the number to experiment with (or just try tweaking the digits, but it will need to pass on LPN and fail on this plugin).
I'm closing this issue as I cannot debug this issue without an example number (which is passing validation with libphonenumber, but failing validation in intl-tel-input). If you can provide that, I will be happy to look into this issue further for you.