Real Canadian Mobile Numbers Marked as Invalid Using isValidNumberPrecise

[isingh1090]

Thanks for your reply.

Yes, you are right that validationNumberType option, is set to mobile numbers and I have tried the real Canadian mobile numbers, and it was returning invalid.

Originally posted by @isingh1090 in #1979

[jackocnr]

Please can you provide a specific example of a Canadian mobile number that is returning invalid?

Which validation method are you using?

Which version of the plugin are you using? (please try updating to the latest version)

[isingh1090]

Thanks for your reply and time.

Method I'm using is isValidNumberPrecise()

Even Demo link (https://intl-tel-input.com/examples/validation.html) returning invalid, for a real Canadian number

I have tried the version v25.2.1 which is not working for me

The version working for me is International Telephone Input v24.5.0

Please let me know if you need more info.

[jackocnr]

Can you check if setting validationNumberTypes to null fixes this?

[meirhlmn]

We are seeing the same problem. Is there any fix or workaround for this?

[jackocnr]

Apologies for the delay in replying.

We use LPN for validation - if you try your number on the LPN demo site, does it say it's valid or invalid?

If the LPN demo site says it's valid, but our website says it's invalid, then please share the full number so I can debug it.

[nzhuk98]

isValidNumberPrecise appears to be completely broken for US numbers as well. I tried multiple real phones (mobile) and they all fail validation with this method, but pass validation on LPN demo site. Also this is test number that used to pass validation and now it's not: 2015550123. It works on LPN.

Setting validationNumberTypes to null makes everything work.

[jackocnr]

Thanks for your help with this. I've just released a fix in v25.4.0 - can you check if that fixes your issue?

[nzhuk98]

Works with v25.4.0 without setting validationNumberTypes to null. Thanks for fixing.