Comments (8)
Thanks @katherinemarsh for highlighting these repo steps. We are currently experiencing the same issue in our implementation. We found this issue after investigating a parsing issue in a previous release of PhoneNumberKit that causes some users to be unable to edit their profile information. Updating to the most current release would resolve our existing issue but exposes this issue you reported, which would prevent a substantial portion of our userbase from logging in with their phone number.
An additional piece of information to share is that we found that verifying in simulator is not sufficient as the issue was not reproducible in simulator but reproduced when built to device.
from phonenumberkit.
I found a temporary workaround here.
You need to make sure you strip out all (
, )
,
, and -
before calling formatPartial.
If the partial formatter picks up a number in the broken format: (3
the partial formatter just returns the raw value you pass in.
So on our end, as the user types values, we strip out the applied formatting before requesting a new value from PhoneNumberKit.
from phonenumberkit.
Thank for reporting that. I can take a look at it, however only after 2 to 3 weeks since I'm don't have access to my computer in that period.
Or if you fix that and open a PR, I will be glad to review it.
from phonenumberkit.
seeing this as well.
can confirm its with all +1 country codes (Canada, US, etc...)
from phonenumberkit.
I found this issue began with this metadata update: ddbc873, yet the issue doesn't exist in https://github.com/google/libphonenumber. I see the metadata on this library is updated frequently to match the libphonenumber metadata, so it's not that specific metadata version causing the issue
from phonenumberkit.
seems the problem is numbers beginning with 3 are not matching this leading numbers regex: [24-9]|3(?:[02-9]|1[1-9])
and getting the wrong number formatter.
My domain knowledge about phone number validation is quite limited, so I don't know if the problem is with the regex itself or not.
Another issue I have noticed is that if you continue typing out the phone number, it never receives the trailing )
after the area code.
So you end up with a number formatted like so: (3333333333
from phonenumberkit.
First off, wanted to thank @BrentMifsud for the workaround!
However, after trying it out in our app, we were still unable to resolve our issues.
Just commenting here to boost awareness again for any contributors -- any help would be greatly appreciated!
from phonenumberkit.
Hey folks!
Do you mind checking if the branch of PR #727 fixes the issue?
from phonenumberkit.
Related Issues (20)
- onPhoneNumberChangeHandler after entering 10digits we are getting value as nil for specific numbers only HOT 3
- onPhoneNumberChangeHandler after entering 10digits we are getting value as nil for specific numbers only
- Unable to parse the mobile number with the Indian region code HOT 1
- From iOS 17 am facing delay in formating phone number HOT 1
- While building Xcode Playgrounds I get an Error: Undefined symbols for architecture x86_64: "___isPlatformVersionAtLeast" HOT 1
- Missing support for textContentType autocomplete with example placeholder + prefix enabled HOT 2
- Build failed because PhoneNumberKit.swiftmodule is not built for arm64 HOT 1
- Cannot find type 'PhoneNumberTextField' in scope & SPM wrong version HOT 1
- It's impossible to identify Mexican numbers with (1) HOT 3
- Please review Austria phone number sample for ios HOT 1
- Setter for 'defaultRegion' is deprecated! HOT 1
- After setting a China number and the flag is set, delete the phone number and add US number. The flag remains China
- Question: Is it safe to initialize PhoneNumberKit on a background thread? HOT 2
- `isValidPhoneNumber` returning true ignoring region HOT 3
- Build Error with Xcode 16 Beta 5 - ParseManager: Mutable capture of 'inout' parameter 'buffer' is not allowed in concurrently-executing code HOT 3
- Jersey partial formatter number issue
- Won't build for Swift 6 HOT 1
- "Mutable capture of 'inout' parameter 'buffer' is not allowed in concurrently-executing code" in XCode 16 beta 5
- Xcode 16 beta 5 ParseManager compile issue
- XCode 16: Mutable capture of 'inout' parameter 'buffer' is not allowed in concurrently-executing code HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from phonenumberkit.