NsdService: Unique id with no client mapping: 209

[nomoreboredom]

Hi Balthazar,

Any idea what may be causing this, which makes the app crash on android devices, Android version 6:

02-08 09:36:05.512 2601-8121/? E/mDnsConnector: SND -> {496 mdnssd stop-resolve 239}
02-08 09:36:05.512 2601-8122/? E/mDnsConnector: RCV <- {200 496 resolve stopped}
02-08 09:36:05.513 2601-8121/? E/mDnsConnector: RMV <- {200 496 resolve stopped}
02-08 09:36:05.513 2601-8121/? E/mDnsConnector: SND -> {497 mdnssd getaddrinfo 240 usn-device-d333.local.}
02-08 09:36:05.514 2601-8122/? E/mDnsConnector: RCV <- {200 497 getAddrInfo started}
02-08 09:36:05.517 2601-8122/? E/mDnsConnector: RCV <- {612 240 "usn-device-d333.local." 120 192.168.1.139}
02-08 09:36:05.517 2601-8121/? E/mDnsConnector: RMV <- {200 497 getAddrInfo started}
02-08 09:36:05.517 2601-8122/? E/mDnsConnector: RCV <- {612 240 "usn-device-d333.local." 120 fe80::2b17:15c7:cc86:1fe0}
02-08 09:36:05.518 2601-8121/? E/mDnsConnector: SND -> {498 mdnssd stop-getaddrinfo 240}
02-08 09:36:05.518 2601-8122/? E/mDnsConnector: RCV <- {200 498 getaddrinfo stopped}
02-08 09:36:05.519 2601-8121/? E/mDnsConnector: RMV <- {200 498 getaddrinfo stopped}
02-08 09:36:05.519 2601-8121/? E/NsdService: Unique id with no client mapping: 240
02-08 09:36:05.519 2601-8121/? E/NsdService: Unhandled { when=-1ms what=393242 obj=com.android.server.NsdService$NativeEvent@b3f5171 target=com.android.internal.util.StateMachine$SmHandler }

There are multiple services broadcasting. Thanks!

[westcode]

I have this issue as well, on every scan a Unique id with no client mapping entry gets added (Unique id with no client mapping). When too many scans are done, the service does not work anymore. I can reproduce this error by performing alot of scans (Android 7.0).

Any idea how to resolve this?

Thanks in advance

[westcode]

@balthazar any idea?