-
Notifications
You must be signed in to change notification settings - Fork 58
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
No IP, TXT records or resolved events #77
Comments
The |
No, as mentioned above we don't receive the resolved events at all unless we call reInit first. |
Wondering if this is a timing issue. Do you kick off your |
Yes, inside the platform.ready callback. I thought timing issue too, so i tried a ten second timer instead. No dice |
Intriguing, thanks for confirming. Some more thoughts...
|
After issuing reInit all the other devices on the network came through as resolved. |
Picking up on a relatively inactive thread here, but I'm also running into this issue with iOS. Particularly, I notice the issue doesn't happen when creating the bonjour service on my Mac - if so then the iOS device picks up the resolved action just fine. But when the service is created on Windows, I'm only left with the "added" action, and it never gets resolved. Did you guys figure it out? |
On Android, for most devices, we get "added" event for most devices, however this event is missing the IP address and TXT record data.
avahi-browse shows all the devices correctly with full info.
I can get it to work by adding a call to reInit() prior to the watch command, however, this really shouldn't be necessary since the app has only just started up.. the reInit() command also takes about 10 seconds to complete.
The text was updated successfully, but these errors were encountered: