servicesDiscovered being fired even when UUIDs aren't found

The story so far:

at 2006-08-11 13:05 jaumedejuan@users.sourceforge.net wrote:
> It doesn't always happen, but sometimes devices that don't have a 
> service with one of the specified UUID's fire a servicesDiscovered in
> the DiscoveryListener.
>
> I have called agent.searchServices() specifying only one UUID which I
> generated myself, so it's unique.
>
> I was running an application in which the servicediscovery was working
> fine. However when a Sony-Ericsson T630 entered the room (which doesn't
> even support JABTW), servicesDiscovered was being fired...
>
> According to the BT API javadoc:
> "searchServices()
> Searches for services on a remote Bluetooth device that have all the
> UUIDs specified in uuidSet."
>
> I have created a workaround in my application by checking for the UUID
> in the ServiceRecord[] array that servicesDiscovered() returns.
>
> I'm attaching a print out of the ServiceRecord supposed to have the
> UUID: 75BC36D7E37B400097A464CD49EF2A85
>
> This print out was generated using the Util.printServiceRecord method
> from the Bluelet application by Ben Hui, available at:
> http://www.benhui.net/modules.php?name=Downloads&d_op=getit&lid=5
>
> By the way, the UUID was created as a long address, so this shouldn't be 
> affected by the other BUG in the tracker that mentions a problem when
> expanding a short UUID to a long UUID.

Original issue reported on code.google.com by paul.tot...@gmail.com on 19 Aug 2006 at 1:24

robertoprato / bluecove

servicesDiscovered being fired even when UUIDs aren't found #3