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
diff --git a/service-t/src/com/android/server/connectivity/mdns/MdnsResponseDecoder.java b/service-t/src/com/android/server/connectivity/mdns/MdnsResponseDecoder.java
index 2115454..7878b0b 100644
--- a/service-t/src/com/android/server/connectivity/mdns/MdnsResponseDecoder.java
+++ b/service-t/src/com/android/server/connectivity/mdns/MdnsResponseDecoder.java
@@ -100,7 +100,7 @@
mdnsPacket = MdnsPacket.parseRecordsSection(reader, flags);
if (mdnsPacket.answers.size() < 1) {
throw new MdnsPacket.ParseException(
- MdnsResponseErrorCode.ERROR_NOT_RESPONSE_MESSAGE, "Response has no answers",
+ MdnsResponseErrorCode.ERROR_NO_ANSWERS, "Response has no answers",
null);
}
return mdnsPacket;