v8.5.1

Hi all,

Please find the new JARs on the maven site here.

The new release contains mostly metadata changes.
Thanks to all those who contributed by providing issue reports!
See detailed release notes.

Want to be notified of future releases? Join the discussion group!

v8.5.0

Hi all,

Please find the new JARs on the maven site here.

The new release contains metadata changes and some code changes. Upgrading to the latest release is always encouraged since phone number information changes often!

New functionality in this release:

• PhoneNumberUtil.canBeInternationallyDialled() API is made public (in Java and C++) now as it is useful for clients if they want to make sure they only allow internationally-accessible numbers for a particular use-case. In JavaScript this API was already public.

Porters only:

• There was a change in the representation of metadata which only affects ports which use the compiled metadata instead of the .xml files. If you use BuildMetadataFromXml.java or the generated metadata files (e.g. PhoneNumberMetadataProto_AD), please see the separate announcement for more details.

Full details in the release notes.

Note if you take advantage of this new functionality by changing your code, it will not necessarily be trivially easy to roll back to a previous version.

Thanks to all those who contributed by providing issue reports!

Want to be notified of future releases? Join the discussion group!

v8.4.3

Hi all,

Please find the new JARs on the maven site here.

The new release contains mostly metadata changes.
Thanks to all those who contributed by providing issue reports!
See detailed release notes.

Want to be notified of future releases? Join the discussion group!

v8.4.2

Hi all,

Please find the new JARs on the maven site here.

The new release contains mostly metadata changes.
Thanks to all those who contributed by providing issue reports!
See detailed release notes.

Porters only:

• Removal of possibleNumberPattern in PhoneNumberMetadata.xml and ShortNumberMetadata.xml as per this announcement. These have been out of use in our library for several months. If you depend on the internal xml implementation and hadn't taken the actions detailed in the announcement, this release may break you.

Want to be notified of future releases? Join the discussion group!

v8.4.1

Hi all,

Please find the new JARs on the maven site here.

The new release contains metadata changes and some code changes. Upgrading to the latest release is always encouraged since phone number information changes often!

Main code changes in this release:

• isPossibleWithReason now returns the new enums INVALID_LENGTH and
  IS_POSSIBLE_LOCAL_ONLY, where these apply. We hope any users of this method have already updated their code appropriately, as per this announcement.

A reminder of example changes you might want to make, if they have not been made already:

• If you are calling isPossible, but you only want to accept possible fully-qualified numbers, you may want to switch to isPossibleWithReason and check for IS_POSSIBLE only.
• If you have a switch statement that generates messages based on the result from isPossibleWithReason you should check that these messages are appropriate for the new values as well. More details about these enums in the code, e.g. thePhoneNumberUtil javadoc

Full details in the release notes.

Thanks to all those who contributed by providing issue reports!

Want to be notified of future releases? Join the discussion group!

v8.4.0

Hi all,

Please find the new JARs on the maven site here.

The new release contains metadata changes
and some code changes. Upgrading to the latest release is always encouraged
since phone number information changes often!

New functionality in this release:

• New API methods: isPossibleNumberForType and isPossibleNumberForTypeWithReason, along with getSupportedTypesForRegion and getSupportedTypesForNonGeoEntity. These allow you to query which types (e.g. Mobile) exist for a particular region, and work out if a number is possible for that type (this is a simple length check) rather than for the region as a whole. This allows for more accurate checks than with the existing API isPossibleNumber which considered lengths of all supported types in a region (e.g. mobile, voicemail, fixed-line, etc.).

Full details in the release notes.

Note if you take advantage of this new functionality by changing your code,
it will not necessarily be trivially easy to roll back to a previous
version.

Thanks to all those who contributed by providing issue reports!

Want to be notified of future releases? Join the discussion group!

v8.3.3

Hi all,

Please find the new JARs on the maven site here.

The new release contains mostly metadata changes.
Thanks to all those who contributed by providing issue reports!
See detailed release notes.

Want to be notified of future releases? Join the discussion group!

v8.3.2

Hi all,

Please find the new JARs on the maven site here.

The new release contains mostly metadata changes.
Thanks to all those who contributed by providing issue reports!
See detailed release notes.

Want to be notified of future releases? Join the discussion group!

v8.3.1

Hi all,

Please find the new JARs on the maven site here.

The new release contains mostly metadata changes.
Thanks to all those who contributed by providing issue reports!
See detailed release notes.

Want to be notified of future releases? Join the discussion group!

v8.3.0

Hi all,

Please find the new JARs on the maven site here.

The new release contains metadata changes and some code changes. Upgrading to the latest release is always encouraged since phone number information changes often!

New functionality in this release:

• Two new ValidationResult enum values have been added, which in a future release will be returned by isPossibleNumberWithReason. Please see this thread on the mailing list for a thorough explanation of changes you might need to make if you use this method.
• isNumberMatch has been improved to better compare numbers which weren't created purely by calling "parse" as recommended.
• C++ only changes: the maximum allowed length for a national significant number was increased to 17 for parity with Java, and the method ExactlySameAs to compare two phone number protos was fixed to also consider the number_of_leading_zeros field.

Full details in the release notes.

Note if you take advantage of the new enums by changing your code, it will not necessarily be trivially easy to roll back to a previous version.

Thanks to all those who contributed by providing issue reports!

Want to be notified of future releases? Join the discussion group!