| commit | 5df1bc4da6f4bb64eb048fc674348eb18af21f0b | [log] [tgz] |
|---|---|---|
| author | Remi NGUYEN VAN <reminv@google.com> | Thu Mar 02 12:59:24 2023 +0900 |
| committer | Remi NGUYEN VAN <reminv@google.com> | Fri Mar 03 12:52:10 2023 +0900 |
| tree | 19a68e237a4000d5e6431d41487341bffd61da64 | |
| parent | 448100884e101cce7413a4bb1478c0bad05e0bf2 [diff] |
Return ERROR_NO_ANSWERS for replies with no answer Only ERROR_NOT_RESPONSE_MESSAGE not considered errors in MdnsMultinetworkSocketClient, so this will cause additional logging and calls to onFailedToParseMdnsResponse callbacks. This matches historical behavior. Bug: 267570781 Test: atest MdnsMultinetworkSocketClientTest Change-Id: I488cc7684135399fd6726f88468119860de2c85f