Currently, the SDK only parses the IPv4 address for an address book entry. With dynamic address book, the service endpoints will be updated to use domain names instead of IPv4 addresses.
Solution
The address book will have either the IPv4 address or the domain name populated. The SDK will need to check for both and, if the domain name is populated, be able to interpret that field correctly for transactions.
Problem
Currently, the SDK only parses the IPv4 address for an address book entry. With dynamic address book, the service endpoints will be updated to use domain names instead of IPv4 addresses.
Solution
The address book will have either the IPv4 address or the domain name populated. The SDK will need to check for both and, if the domain name is populated, be able to interpret that field correctly for transactions.
Alternatives
No response