base on A Swift framework for parsing, formatting and validating international phone numbers. Inspired by Google's libphonenumber.  [](http://cocoapods.org/?q=PhoneNumberKit)  [](http://cocoapods.org/?q=PhoneNumberKit) [](https://github.com/Carthage/Carthage) # PhoneNumberKit Swift 5.3 framework for parsing, formatting and validating international phone numbers. Inspired by Google's libphonenumber. ## Features | | Features | | ---------------- | ------------------------------------------------------------------------------------------- | | :phone: | Validate, normalize and extract the elements of any phone number string. | | :100: | Simple Swift syntax and a lightweight readable codebase. | | :checkered_flag: | Fast. 1000 parses -> ~0.4 seconds. | | :books: | Best-in-class metadata from Google's libPhoneNumber project. | | :trophy: | Fully tested to match the accuracy of Google's JavaScript implementation of libPhoneNumber. | | :iphone: | Built for iOS. Automatically grabs the default region code from the phone. | | 📝 | Editable (!) AsYouType formatter for UITextField. | | :us: | Convert country codes to country names and vice versa | ## Usage Import PhoneNumberKit at the top of the Swift file that will interact with a phone number. ```swift import PhoneNumberKit ``` All of your interactions with PhoneNumberKit happen through a PhoneNumberUtility object. The first step you should take is to allocate one. A PhoneNumberUtility instance is relatively expensive to allocate (it parses the metadata and keeps it in memory for the object's lifecycle), you should try and make sure PhoneNumberUtility is allocated once and deallocated when no longer needed. ```swift let phoneNumberUtility = PhoneNumberUtility() ``` To parse a string, use the parse function. The region code is automatically computed but can be overridden if needed. PhoneNumberKit automatically does a hard type validation to ensure that the object created is valid, this can be quite costly performance-wise and can be turned off if needed. ```swift do { let phoneNumber = try phoneNumberUtility.parse("+33 6 89 017383") let phoneNumberCustomDefaultRegion = try phoneNumberUtility.parse("+44 20 7031 3000", withRegion: "GB", ignoreType: true) } catch { print("Generic parser error") } ``` If you need to parse and validate a large amount of numbers at once, PhoneNumberKit has a special, lightning fast array parsing function. The default region code is automatically computed but can be overridden if needed. Here you can also ignore hard type validation if it is not necessary. Invalid numbers are ignored in the resulting array. ```swift let rawNumberArray = ["0291 12345678", "+49 291 12345678", "04134 1234", "09123 12345"] let phoneNumbers = phoneNumberUtility.parse(rawNumberArray) let phoneNumbersCustomDefaultRegion = phoneNumberUtility.parse(rawNumberArray, withRegion: "DE", ignoreType: true) ``` PhoneNumber objects are immutable Swift structs with the following properties: ```swift phoneNumber.numberString phoneNumber.countryCode phoneNumber.nationalNumber phoneNumber.numberExtension phoneNumber.type // e.g Mobile or Fixed ``` Formatting a PhoneNumber object into a string is also very easy ```swift phoneNumberUtility.format(phoneNumber, toType: .e164) // +61236618300 phoneNumberUtility.format(phoneNumber, toType: .international) // +61 2 3661 8300 phoneNumberUtility.format(phoneNumber, toType: .national) // (02) 3661 8300 ``` ## PhoneNumberTextField  To use the AsYouTypeFormatter, just replace your UITextField with a PhoneNumberTextField (if you are using Interface Builder make sure the module field is set to PhoneNumberKit). You can customize your TextField UI in the following ways - `withFlag` will display the country code for the `currentRegion`. The `flagButton` is displayed in the `leftView` of the text field with it's size set based off your text size. - `withExamplePlaceholder` uses `attributedPlaceholder` to show an example number for the `currentRegion`. In addition when `withPrefix` is set, the country code's prefix will automatically be inserted and removed when editing changes. PhoneNumberTextField automatically formats phone numbers and gives the user full editing capabilities. If you want to customize you can use the PartialFormatter directly. The default region code is automatically computed but can be overridden if needed (see the example given below). ```swift class MyGBTextField: PhoneNumberTextField { override var defaultRegion: String { get { return "GB" } set {} // exists for backward compatibility } } ``` ```swift let textField = PhoneNumberTextField() PartialFormatter().formatPartial("+336895555") // +33 6 89 55 55 ``` You can also query countries for a dialing code or the dialing code for a given country ```swift phoneNumberUtility.countries(withCode: 33) phoneNumberUtility.countryCode(for: "FR") ``` ## Customize Country Picker You can customize colors and fonts on the Country Picker View Controller by overriding the property "withDefaultPickerUIOptions" ```swift let options = CountryCodePickerOptions( backgroundColor: UIColor.systemGroupedBackground separatorColor: UIColor.opaqueSeparator textLabelColor: UIColor.label textLabelFont: .preferredFont(forTextStyle: .callout) detailTextLabelColor: UIColor.secondaryLabel detailTextLabelFont: .preferredFont(forTextStyle: .body) tintColor: UIView().tintColor cellBackgroundColor: UIColor.secondarySystemGroupedBackground cellBackgroundColorSelection: UIColor.tertiarySystemGroupedBackground ) textField.withDefaultPickerUIOptions = options ``` Or you can change it directly: ```swift textField.withDefaultPickerUIOptions.backgroundColor = .red ``` Please refer to `CountryCodePickerOptions` for more information about usage and how it affects the view. ## Need more customization? You can access the metadata powering PhoneNumberKit yourself, this enables you to program any behaviours as they may be implemented in PhoneNumberKit itself. It does mean you are exposed to the less polished interface of the underlying file format. If you program something you find useful please push it upstream! ```swift phoneNumberUtility.metadata(for: "AU")?.mobile?.exampleNumber // 412345678 ``` ### [Preferred] Setting up with [Swift Package Manager](https://swiftpm.co/?query=PhoneNumberKit) The [Swift Package Manager](https://swift.org/package-manager/) is now the preferred tool for distributing PhoneNumberKit. From Xcode 11+ : 1. Select File > Swift Packages > Add Package Dependency. Enter `https://github.com/marmelroy/PhoneNumberKit.git` in the "Choose Package Repository" dialog. 2. In the next page, specify the version resolving rule as "Up to Next Major" from "3.7.0". 3. After Xcode checked out the source and resolving the version, you can choose the "PhoneNumberKit" library and add it to your app target. For more info, read [Adding Package Dependencies to Your App](https://developer.apple.com/documentation/xcode/adding_package_dependencies_to_your_app) from Apple. Alternatively, you can also add PhoneNumberKit to your `Package.swift` file: ```swift dependencies: [ .package(url: "https://github.com/marmelroy/PhoneNumberKit", from: "3.7.0") ] ``` ### Setting up with Carthage [Carthage](https://github.com/Carthage/Carthage) is a decentralized dependency manager that automates the process of adding frameworks to your Cocoa application. You can install Carthage with [Homebrew](http://brew.sh/) using the following command: ```bash $ brew update $ brew install carthage ``` To integrate PhoneNumberKit into your Xcode project using Carthage, specify it in your `Cartfile`: ```ogdl github "marmelroy/PhoneNumberKit" ``` ### Setting up with [CocoaPods](http://cocoapods.org/?q=PhoneNumberKit) ```ruby pod 'PhoneNumberKit', '~> 3.7' ``` ", Assign "at most 3 tags" to the expected json: {"id":"11416","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"