Skip to content
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

Open
TomMettam opened this issue Apr 8, 2019 · 7 comments
Open

No IP, TXT records or resolved events #77

TomMettam opened this issue Apr 8, 2019 · 7 comments

Comments

@TomMettam
Copy link

TomMettam commented Apr 8, 2019

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.

@emcniece
Copy link
Collaborator

emcniece commented Apr 8, 2019

The resolved event is the one for detecting addresses - do your expected details show up in there?

@TomMettam
Copy link
Author

No, as mentioned above we don't receive the resolved events at all unless we call reInit first.

@emcniece
Copy link
Collaborator

emcniece commented Apr 8, 2019

Wondering if this is a timing issue. Do you kick off your watch() from inside (or after) a platform.ready() or similar call?

@TomMettam
Copy link
Author

Yes, inside the platform.ready callback. I thought timing issue too, so i tried a ten second timer instead. No dice

@emcniece
Copy link
Collaborator

emcniece commented Apr 8, 2019

Intriguing, thanks for confirming. Some more thoughts...

  • Mobile data enabled on the Android devices? Does disabling mobile data change anything?
  • Anything interesting in adb logs (either in terminal or Android Studio) pertaining to network status or this plugin?
  • You say "for most devices" - are there specific devices that are reliable, or does it vary on each app boot?

@TomMettam
Copy link
Author

  • No mobile data, wifi only.

  • Nothing interesting that I could see. Network connectivity was solid and I could see the query and responses with wireshark.

  • Only one device came through as "resolved" (and actually this event fired repeatedly). It was a synology NAS device which was itself performing mdns queries.

After issuing reInit all the other devices on the network came through as resolved.

@tonetechnician
Copy link

tonetechnician commented Mar 28, 2020

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants