Android bound service not destroyed after all clients unbind

Asked Dec 18 '20 at 10:22

Active Dec 18 '20 at 10:22

Viewed 180 times

I have 2 services A and B.

A creates B and binds to B via the Context#bindService() with the CONTEXT_AUTO_CREATE flag. Normally when A unbinds from B, B is destroyed. Under this approach, A and B are running in the same process with A's package name.

I need B running in a separate process, so I added a android:process flag to B's AndroidManifest.xml. This way, when A binds & auto-creates B, B will run a separate process from A.

However, I noticed that when A unbinds from B, B continues to be up. This is against the Android Developer guide on bound processes - that a service is not considered "started" if Service#onStartCommand() is not called. As a matter of fact, onStartCommand() is never called. But when all clients unbind from B, B continues to run. Why is that? Is there a way to resolve this issue?

Any help is appreciated

asked Dec 18 '20 at 10:22

mango

How do you know that B is still running? – David Wasser Dec 18 '20 at 11:19
because i ran `adb shell ps` and still see B. Normally B would not be listed – mango Dec 19 '20 at 01:43

Android bound service not destroyed after all clients unbind

0 Answers0