site_archiver@lists.apple.com Delivered-To: macnetworkprog@lists.apple.com On 3 May 2017, at 18:20, Marc Krochmal <marc@apple.com> wrote:
I'm not sure why you're getting stream errors …
Indeed. I tried this on a test app here in my office and I was able to reconnect just fine. On 3 May 2017, at 17:38, Jeff Kelley <slaunchaman@gmail.com> wrote:
It seems like I can’t just call getInputStream(_:outputStream:) again on the resolved service, as doing so gives me all kinds of errors about a socket not being available.
Can you post more details about the actual error you’re getting?
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. Share and Enjoy -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40lists... This email sent to site_archiver@lists.apple.com