search

tajchert / BusWear

EventBus for Android Wear devices.
Apache License 2.0
257 stars 23 forks source link

W/WearableService﹕ Unable to pick WearableListenerService too many services defined. #4

Open greenspand opened 9 years ago

greenspand commented 9 years ago

HI, I Recently used the BusWear library and it worked like a charm until yesterday. I was debugging my mobile app and, while posting from the wearable I got this message, 1 per event: W/WearableService﹕ Unable to pick WearableListenerService for ro.sorin.remotepal, too many services defined. I have followed by letter the implementation guideline.

tajchert commented 9 years ago

So you defined your own WearableListenerService. Library defines one, and you cannot define one more (limited by system). I have created another library to solve it https://github.com/tajchert/ServiceWear it allows you to define more than one WearableListenerService using BroadcastReceivers, however you need to create fork of BusWear library and add it manually to it. I'm leaving this issue open until I or somebody else will do so.

tajchert commented 8 years ago

Also this is addressed by @btkelly PR #10 . I would love to discuss and find best solution for this. Any opinion @mg6maciej on that? As you are the person that pushed me towards grade overriding tag instead of manually adding in Manifest (and also expert in clean-code approach).

greenspand commented 8 years ago

My sugestion is to place the ServiceWear in the BusWear library as default. This way, if someone wants to use the traditional way of calling the googleApi for msgs and data he/ she can still use the ServiceWear. And in the case of BusWear if it's basked in it solves the one single Service issue without the user eaven knowing it.

tajchert commented 8 years ago

Yup, that make probably most sense.