[1.2] Failed to resolve service '75E232F7505D0C92': 3

[shuiYe-704265085]

Reproduction steps

When I tried to discover devices through the deviceController.discoverCommissionableNodes() function, I found that only one device could be discovered at a time. When multiple devices could be discovered simultaneously, the console log displayed as follows

2024-02-04 15:10:28.635 23920-23920/com.akuvox.mattersdkdemo D/NsdManagerServiceBrowser: Starting service discovering for '_matterc._udp'
2024-02-04 15:10:28.642 23920-24850/com.akuvox.mattersdkdemo I/NsdManagerServiceBrowser: Started service '_matterc._udp'
2024-02-04 15:10:28.642 23920-24850/com.akuvox.mattersdkdemo I/NsdManagerServiceBrowser: Found service '93962EB963ADF462'
2024-02-04 15:10:28.642 23920-24850/com.akuvox.mattersdkdemo I/NsdManagerServiceBrowser: Found service '75E232F7505D0C92'
2024-02-04 15:10:33.641 23920-23920/com.akuvox.mattersdkdemo D/NsdManagerServiceResolver: resolve: Starting service resolution for '93962EB963ADF462' type '_matterc._udp'
2024-02-04 15:10:33.643 23920-23920/com.akuvox.mattersdkdemo D/NsdManagerServiceResolver: resolve: Starting service resolution for '75E232F7505D0C92' type '_matterc._udp'
2024-02-04 15:10:33.649 23920-24850/com.akuvox.mattersdkdemo W/NsdManagerServiceBrowser: Succeed to stop discovery service '_matterc._udp
2024-02-04 15:10:33.660 23920-24850/com.akuvox.mattersdkdemo D/NsdServiceFinderAndResolver: Service discovery started. regType: _matterc._udp
2024-02-04 15:10:33.672 23920-24850/com.akuvox.mattersdkdemo D/NsdServiceFinderAndResolver: Service discovery started. regType: _matterc._udp
2024-02-04 15:10:33.672 23920-24850/com.akuvox.mattersdkdemo D/NsdServiceFinderAndResolver: onServiceFound: found target service name: 93962EB963ADF462, type: _matterc._udp., host: null, port: 0, txtRecord: 
2024-02-04 15:10:33.673 23920-24850/com.akuvox.mattersdkdemo D/NsdServiceFinderAndResolver: onServiceFound: found service not a target for resolution, ignoring name: 75E232F7505D0C92, type: _matterc._udp., host: null, port: 0, txtRecord: 
2024-02-04 15:10:33.676 23920-24850/com.akuvox.mattersdkdemo I/NsdServiceFinderAndResolver: Discovery stopped: _matterc._udp
2024-02-04 15:10:33.679 23920-24850/com.akuvox.mattersdkdemo D/NsdServiceFinderAndResolver: onServiceFound: found service not a target for resolution, ignoring name: 93962EB963ADF462, type: _matterc._udp., host: null, port: 0, txtRecord: 
2024-02-04 15:10:33.679 23920-24850/com.akuvox.mattersdkdemo D/NsdServiceFinderAndResolver: onServiceFound: found target service name: 75E232F7505D0C92, type: _matterc._udp., host: null, port: 0, txtRecord: 
2024-02-04 15:10:33.682 23920-24850/com.akuvox.mattersdkdemo I/NsdServiceFinderAndResolver: Discovery stopped: _matterc._udp
2024-02-04 15:10:33.682 23920-24850/com.akuvox.mattersdkdemo W/NsdServiceFinderAndResolver: Failed to resolve service '75E232F7505D0C92': 3
2024-02-04 15:10:33.692 23920-24850/com.akuvox.mattersdkdemo I/NsdServiceFinderAndResolver: Resolved service '93962EB963ADF462' to /192.168.1.113, type : ._matterc._udp
2024-02-04 15:10:33.693 23920-24850/com.akuvox.mattersdkdemo D/DIS:  ----- entry [0] : D 4045
2024-02-04 15:10:33.693 23920-24850/com.akuvox.mattersdkdemo D/DIS:  ----- entry [1] : T 1
2024-02-04 15:10:33.693 23920-24850/com.akuvox.mattersdkdemo D/DIS:  ----- entry [2] : CM 1
2024-02-04 15:10:33.693 23920-24850/com.akuvox.mattersdkdemo D/DIS:  ----- entry [3] : PH 36
2024-02-04 15:10:33.693 23920-24850/com.akuvox.mattersdkdemo D/DIS:  ----- entry [4] : PI NULL
2024-02-04 15:10:33.693 23920-24850/com.akuvox.mattersdkdemo D/DIS:  ----- entry [5] : RI 0301553349C2F37A81D4FADF04B3B4465A71
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS:  ----- entry [6] : VP 5020+903
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS:  ----- entry [7] : TRI 153010103138383738323764333664613835643825110301301210A95E8988FFB836CD4C2052A75DD7BD7A291318
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS:  ----- entry [8] : TCAS 0
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: Discovered node:
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	Hostname: 192.168.1.113
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	IP Address #1: 192.168.1.113
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	Port: 5540
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	Mrp Interval idle: not present
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	Mrp Interval active: not present
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	TCP Supported: 1
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	Rotating ID: 0301553349C2F37A81D4FADF04B3B4465A71
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	Vendor ID: 5020
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	Product ID: 903
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	Long Discriminator: 4045
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	Pairing Hint: 36
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	Instance Name: 93962EB963ADF462
2024-02-04 15:10:33.694 23920-24850/com.akuvox.mattersdkdemo D/DIS: 	Commissioning Mode: 1

I want to know why the device 75E232F7505D0C92 cannot be added to the list, and it is normal when there is only one device 75E232F7505D0C92

Bug prevalence

etc

GitHub hash of the SDK that was being used

d1b59df

Platform

android

Platform Version(s)

No response

Type

Platform Issue

Anything else?

No response