Fixed that bad ADN record loading caused all other good records dropped.
Fixed the issue that while loading all ADN records from EF_ADN, if one of the record is bad, for example, it points to an EF_EXT1 for the rest of the phone number, but EF_EXT1 does not exist, we will skip that bad record but still keep the rest of the good records from EF_ADN. bug: 23163512 Change-Id: I4828f346769640f1fbc95d49849c61b52d043846
Loading
Please register or sign in to comment