Android Service - startService is called multiple times and causes value mixup...

Question

I have some conditional calls from my code which starts same service with different data values passed through bundle to that service. When I checked for only one condition met, service works fine for all conditions. But when 2 or more conditions match, these calls this same service but with different data values in bundle. Problem is when this scenario is met the values sent by first call are not getting replaced for second condition to start same service. So service is responding wrongly.

It is like this

if(some cond)
{
    some values in serivce intent bundle.startService(serviceintent1);
}
if(some cond)
{
    some data in intent bundle.startService(serviceintent1);
}

When both conditions are met then call to startService is twice. but I am getting values from first condition in second condition startService call.

Help me in this issue...

Can you post your code in order to understand what the problem is? — citizen conn, Jun 18 '11 at 21:55
Can you use an if-else-if statement? Or replace your Service with an IntentService that will queue the requests to be executed in a worker thread? — Glendon Trullinger, Jun 18 '11 at 22:04

Tosa · Accepted Answer · 2018-02-15T00:08:03.827

3

What is your return type in onStartCommand ?

You should read about the life cycle of the service. https://developer.android.com/reference/android/app/Service.html#ServiceLifecycle

I would suggest to use IntentService, as it is designed for handling asyncron tasks, it also start in a worker thread. http://developer.android.com/reference/android/app/IntentService.html

To really help you, the code of your service is quite important :)

edited Feb 15 '18 at 00:08

answered Jun 18 '11 at 22:30

Tosa

658
5
15

This helped a lot; didn't think to look at my return type. Thanks. – midiwriter May 27 '13 at 05:29
1

I think your first link should be https://developer.android.com/reference/android/app/Service.html#ServiceLifecycle ServiceLifecycle vs ProcessLifecycle – Alon Feb 14 '18 at 23:17

score 0 · Answer 2 · edited May 23 '17 at 12:29

0

Have a look at Bind service to activity in Android the question .. where the difference between startservice and bindservice is discussed.. I guess this could solve your problem.

edited May 23 '17 at 12:29

Community

1
1

answered Jun 19 '11 at 01:05

success_anil

3,659
3
27
31

Android Service - startService is called multiple times and causes value mixup...

2 Answers2

Linked