Fixed
Status Update
Comments
en...@google.com <en...@google.com>
to...@gmail.com <to...@gmail.com> #3
"Priority-Small" it looks that it will be never fixed.
I don't understand why almost every Android API has issue that prevent to use it :-(
I don't understand why almost every Android API has issue that prevent to use it :-(
ge...@gmail.com <ge...@gmail.com> #4
That's why Android sucks! The overall idea is good but execution...
Update distribution model also pushes developers away - even if API bug gets fixed in e.g. 5.3 - there is no guarantee the last year flagship phones will ever see that update (except Google Play Edition and Nexus lines). All other phones that still running Ice Cream Sandwich - forget it..
Update distribution model also pushes developers away - even if API bug gets fixed in e.g. 5.3 - there is no guarantee the last year flagship phones will ever see that update (except Google Play Edition and Nexus lines). All other phones that still running Ice Cream Sandwich - forget it..
mi...@gmail.com <mi...@gmail.com> #5
The service discovery is pretty useless without being able to read the attributes.
mi...@gmail.com <mi...@gmail.com> #6
not even the port and the address can be read (using a standard avahi "services" definition)
ge...@gmail.com <ge...@gmail.com> #7
Android 6.0 is here and the bug still open, NSD discovery still not usable... Even Win got it right in the version 10.
st...@gmail.com <st...@gmail.com> #8
For those still troubled by this bug: I have developed a workaround to manually fetch the TXT record over the wire when NsdManager notifies of a new service. This has been open sourced as a library under the MIT License: https://github.com/youviewtv/tinydnssd
jo...@joshpearl.com <jo...@joshpearl.com> #9
I'm slightly confused here. It seems that these API methods are entirely unusable. Am I missing something?
mo...@google.com <mo...@google.com> #11
Regarding comment 6: To read any more than the most basic information you have to resolve the the service as described here http://developer.android.com/reference/android/net/nsd/NsdManager.html .
In Android M even to resolveService call does not load the TXT information though.
In Android M even to resolveService call does not load the TXT information though.
mo...@google.com <mo...@google.com>
ry...@gmail.com <ry...@gmail.com> #14
Why not mark the documentation of the methods as UNIMPLEMENTED until the next release?
an...@gmail.com <an...@gmail.com> #15
Can someone from Google please commit when this issue will get resolved?
mo...@google.com <mo...@google.com> #16
I marked the bug as "future release". This means that it will be fixes in a release that at the point I marked it was in the future. In reality the fix did already appear in the latest Android N developer preview.
This will not be fixed for Android M and before. For these releases you have to rely on 3rd party libs.
This will not be fixed for Android M and before. For these releases you have to rely on 3rd party libs.
Description
serviceInfo.setAttribute(key,value) writes attribute Ok (discoverable via third-party libs and other platforms);
Native Android APIs NsdServiceInfo.getAttributes() and NsdServiceInfo.getAttribute(key)calls both return empty arrays. Third-party zero-conf libs read attributes as expected.