isBound is not reliable about android-beacon-library HOT 5 CLOSED

Good catch. The issue is that the serviceMessenger is not set to null when the service disconnects, so the isBound() method returns the wrong value.

Fixed in beecedf

from android-beacon-library.

It sounds like onServiceDisconnected may only be called in the event of the service crashing. I cloned the latest commit and it does not seem to be called when I go through the normal unbinding process.

It seems like an alternate solution will be necessary.

from android-beacon-library.

If there is no callback in the service when the last consumer unbinds, then I suppose it would be possible to track it simply by the number of consumers. Perhaps in the unbind method, we could simply change:

consumers.remove(consumer);

to

consumers.remove(consumer);
if (consumers.size() == 0) {
    // If this is the last consumer to disconnect, the service will exit
    // release the serviceMessenger.
    serviceMessenger = null;
}

@sjones512, since you clearly have a test case queued up, do you want to give this a try?

from android-beacon-library.

This appears to work. The next time getInstanceForApplication is called in onCreate the serviceMessenger is null and isBound returns False.

from android-beacon-library.

Changed in 2b0d4ed

from android-beacon-library.