-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zeroconf.ZeroconfHost.AddService (Zeroconf.IService service) Null Key Exception - iOS, Bug #244
Comments
So the exception comes from here: Zeroconf/Zeroconf/ZeroconfRecord.cs Line 193 in 238df25
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 Zeroconf/Zeroconf/BonjourBrowser.cs Lines 399 to 402 in 238df25
|
twofingerrightclick
changed the title
Zeroconf.ZeroconfHost.AddService (Zeroconf.IService service) Exception null Key
Zeroconf.ZeroconfHost.AddService (Zeroconf.IService service) Null Key Exception Bug
Aug 17, 2022
@clairernovotny Please review #246 |
twofingerrightclick
changed the title
Zeroconf.ZeroconfHost.AddService (Zeroconf.IService service) Null Key Exception Bug
Zeroconf.ZeroconfHost.AddService (Zeroconf.IService service) Null Key Exception - iOS, Bug
Aug 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: