Open twofingerrightclick opened 2 years ago
So the exception comes from here: https://github.com/novotnyllc/Zeroconf/blob/238df25a26d2b0f214d7eee20f3d6a1e105ee9b8/Zeroconf/ZeroconfRecord.cs#L193 The ServiceName on the Service object is not being set (is null) as part of the iOS pipeline of the ResolveAsync. I will see if I can figure out where the ServiceName is supposed to be set, but isn't - Nullable enabled would be helpful here.
I am thinking it should have been set about here in the BonjourBrowser.cs https://github.com/novotnyllc/Zeroconf/blob/238df25a26d2b0f214d7eee20f3d6a1e105ee9b8/Zeroconf/BonjourBrowser.cs#L399-L402
@clairernovotny Please review https://github.com/novotnyllc/Zeroconf/pull/246
Using latest stable Zeroconf 3.6.11 I am trying to get an iOS Xamarin project working for iOS 14.5+ (previously worked on iOS versions prior). It only needs to search for a single service and so I have followed the instructions for adding
NSBonjourServices
in theInfo.plist
:When calling
ZeroconfResolver.ResolveAsync("_printer._tcp.local.")
the following exception bubbles up from Zeroconf.ZeroconfHost.AddService (Zeroconf.IService service):ZeroconfResolver.IsiOSWorkaroundEnabled
resolves to true.I am trying to run the demo iOS project included in the repo to confirm similar behavior, but I currently can get it working... it builds and deploys, but is just a black screen.