balthazar
Failure to resolve results in halted search
Sometimes bad IPv6 addresses make their way into a Bonjour record (I'm not sure how, but this has happened a fair amount during testing, oddly with %en0 as the last part of the address). As such, any running search trying to resolve this bad IP not only fails to trigger "resolve", but also then triggers "error" and promptly stops searching.
What I expect the package to do is disregard this IP address and continue - only if none of the addresses resolve should it error, and even then, it shouldn't end the search.
I intend on raising a PR for this shortly.
I had every intention of fixing this, and I'm sure I developed a patch somewhere, but we also encountered more issues with Bonjour and MDNS on our other systems due to other bad libraries.
Ultimately, we've moved away from React Native now and I can't remember whether it was crashing out in the native code, or the JS code, nor can I remember whether the issue was specific to iOS or Android. Having taken a quick glance at the iOS code, I'd probably put a bunch of debugging around this bit and work from there: https://github.com/balthazar/react-native-zeroconf/blob/master/ios/RNZeroconf/RNNetServiceSerializer.m#L52