Thanks for the replies! I found the issue and it was completely unrelated. On the host side, I was stopping the service prematurely. Now that I keep the service alive for the duration of the connection, it’s working great.
On Thu, May 4, 2017 at 3:45 AM, Quinn "The Eskimo!" <[email protected]> wrote: > > > My next thing to try will be to rediscover the service, using its TXT > data to make sure it’s the same one, re-resolve the address, and try again. > > As Marc noted, you could (and should) avoid that rediscovery by making a > copy of the NSNetService. Thanks for the tip—I was working on reconnection logic when this came in, and making a copy sounds way easier! Jeff Kelley [email protected] | @SlaunchaMan <https://twitter.com/SlaunchaMan> | jeffkelley.org
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to [email protected]
